Terminal device, base station device, communication method, and integrated circuit

ABSTRACT

Uplink data is transmitted efficiently. A terminal device configured to: in a case that a difference between an uplink transmission timing for a Timing Advance Group including a primary cell of a master cell group and an uplink transmission timing for a Secondary Timing Advance Group of a secondary cell group exceeds a maximum transmission timing difference, consider that a timer for the Secondary Timing Advance Group of the secondary cell group has expired and stop transmission on a physical uplink shared channel in the Secondary Timing Advance Group of the secondary cell group.

TECHNICAL FIELD

The present invention relates to a terminal device, a base stationdevice, a communication method, and an integrated circuit.

This application claims priority based on JP 2015-185159 filed on Sep.18, 2015, the contents of which are incorporated herein by reference.

BACKGROUND ART

In the 3rd Generation Partnership Project (3GPP), a radio access methodand a radio network for cellular mobile communications (hereinafter,referred to as “Long Term Evolution (LTE)”, or “Evolved UniversalTerrestrial Radio Access (EUTRA)”) have been studied (NPL. 1). In LTE, abase station device is also referred to as an evolved NodeB (eNodeB),and a terminal device is also referred to as User Equipment (UE). LTE isa cellular communication system in which multiple areas each covered bythe base station device are deployed to form a cellular structure. Insuch a cellular communication system, a single base station device maymanage multiple cells.

LTE supports a Time Division Duplex (TDD). LTE that employs the TDDscheme is also referred to as TD-LTE or LTE TDD. In TDD, uplink signalsand downlink signals are time division multiplexed. Furthermore, LTEsupports a Frequency Division Duplex (FDD).

In 3GPP, latency reduction enhancements have been studied. For example,for the latency reduction enhancements, Scheduling request first grantor Pre-scheduled first grant has been studied (NPL. 2).

CITATION LIST Non Patent Literature

-   NPL 1: “3GPP TS 36.321 V12.6.0 (2015-06) Evolved Universal    Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC)    protocol specification (Release 12)”, 8 Jul. 2015.-   NPL 2:“L2 enhancements to reduce latency”, R2-153490, Ericsson, 3GPP    TSG-RAN WG2 #91, Beijing, China, 24-28 Aug. 2015.

SUMMARY OF INVENTION Technical Problem

However, for the radio communication system as described above, aconcrete procedure when transmitting uplink data has not beensufficiently studied.

The present invention has been made in light of the foregoing, and anobject of the present invention is to provide a terminal device, a basestation device, a communication method, and an integrated circuit, whichenable efficient transmission of uplink data.

Solution to Problem

(1) To accomplish the object described above, aspects of the presentinvention are contrived to provide the following measures. Specifically,a terminal device according to an aspect of the present invention isconfigured to: in a case that a difference between an uplinktransmission timing for a Timing Advance Group including a primary cellof a master cell group and an uplink transmission timing for a SecondaryTiming Advance Group of a secondary cell group exceeds a maximumtransmission timing difference, consider that a timer for the SecondaryTiming Advance Group of the secondary cell group has expired, and stoptransmission on a physical uplink shared channel in the Secondary TimingAdvance Group of the secondary cell group; and in a case that adifference between an uplink transmission timing for a Timing AdvanceGroup including a primary secondary cell of the secondary cell group andan uplink transmission timing for the Secondary Timing Advance Group ofthe secondary cell group exceeds a maximum transmission timingdifference, consider that the timer for the Secondary Timing AdvanceGroup of the secondary cell group has expired, and stop the transmissionon the physical uplink shared channel in the Secondary Timing AdvanceGroup of the secondary cell group.

(2) A base station device according to an aspect of the presentinvention is configured to: in a case that a difference between anuplink transmission timing for a terminal device in a Timing AdvanceGroup including a primary cell of a master cell group and an uplinktransmission timing for the terminal device in a Secondary TimingAdvance Group of a secondary cell group exceeds a maximum transmissiontiming difference, consider that a timer for the Secondary TimingAdvance Group of the secondary cell group has expired and transmissionon a physical uplink shared channel in the Secondary Timing AdvanceGroup of the secondary cell group is to be stopped; and in a case that adifference between an uplink transmission timing for a terminal devicein a Timing Advance Group including a primary secondary cell of thesecondary cell group and an uplink transmission timing for the terminaldevice in the Secondary Timing Advance Group of the secondary cell groupexceeds a maximum transmission timing difference, consider that thetimer for the Secondary Timing Advance Group of the secondary cell grouphas expired and the transmission on the physical uplink shared channelin the Secondary Timing Advance Group of the secondary cell group is tobe stopped.

(3) A communication method of a terminal device according to an aspectof the present invention includes the steps of: in a case that adifference between an uplink transmission timing for a Timing AdvanceGroup including a primary cell of a master cell group and an uplinktransmission timing for a Secondary Timing Advance Group of a secondarycell group exceeds a maximum transmission timing difference, consideringthat a timer for the Secondary Timing Advance Group of the secondarycell group has expired, and stopping transmission on a physical uplinkshared channel in the Secondary Timing Advance Group of the secondarycell group; and in a case that a difference between an uplinktransmission timing for a Timing Advance Group including a primarysecondary cell of the secondary cell group and an uplink transmissiontiming for the Secondary Timing Advance Group of the secondary cellgroup exceeds a maximum transmission timing difference, considering thatthe timer for the Secondary Timing Advance Group of the secondary cellgroup has expired, and stopping the transmission on the physical uplinkshared channel in the Secondary Timing Advance Group of the secondarycell group.

(4) A communication method of a base station device according to anaspect of the present invention includes the steps of: in a case that adifference between an uplink transmission timing for a terminal devicein a Timing Advance Group including a primary cell of a master cellgroup and an uplink transmission timing for the terminal device in aSecondary Timing Advance Group of a secondary cell group exceeds amaximum transmission timing difference, considering that a timer for theSecondary Timing Advance Group of the secondary cell group has expiredand transmission on a physical uplink shared channel in the SecondaryTiming Advance Group of the secondary cell group is to be stopped; andin a case that a difference between an uplink transmission timing for aterminal device in a Timing Advance Group including a primary secondarycell of the secondary cell group and an uplink transmission timing forthe terminal device in the Secondary Timing Advance Group of thesecondary cell group exceeds a maximum transmission timing difference,considering that the timer for the Secondary Timing Advance Group of thesecondary cell group has expired and the transmission on the physicaluplink shared channel in the Secondary Timing Advance Group of thesecondary cell group is to be stopped.

(5) An integrated circuit to be mounted on a terminal device, theintegrated circuit causing the terminal device to perform functions to:in a case that a difference between an uplink transmission timing for aTiming Advance Group including a primary cell of a master cell group andan uplink transmission timing for a Secondary Timing Advance Group of asecondary cell group exceeds a maximum transmission timing difference,consider that a timer for the Secondary Timing Advance Group of thesecondary cell group has expired, and stop transmission on a physicaluplink shared channel in the Secondary Timing Advance Group of thesecondary cell group; and in a case that a difference between an uplinktransmission timing for a Timing Advance Group including a primarysecondary cell of the secondary cell group and an uplink transmissiontiming for the Secondary Timing Advance Group of the secondary cellgroup exceeds a maximum transmission timing difference, consider thatthe timer for the Secondary Timing Advance Group of the secondary cellgroup has expired, and stop the transmission on the physical uplinkshared channel in the Secondary Timing Advance Group of the secondarycell group.

(6) An integrated circuit to be mounted on a base station device, theintegrated circuit causing the base station device to perform functionsto: in a case that a difference between an uplink transmission timingfor a terminal device in a Timing Advance Group including a primary cellof a master cell group and an uplink transmission timing for theterminal device in a Secondary Timing Advance Group of a secondary cellgroup exceeds a maximum transmission timing difference, consider that atimer for the Secondary Timing Advance Group of the secondary cell grouphas expired and transmission on a physical uplink shared channel in theSecondary Timing Advance Group of the secondary cell group is to bestopped; and in a case that a difference between an uplink transmissiontiming for a terminal device in a Timing Advance Group including aprimary secondary cell of the secondary cell group and an uplinktransmission timing for the terminal device in the Secondary TimingAdvance Group of the secondary cell group exceeds a maximum transmissiontiming difference, consider that the timer for the Secondary TimingAdvance Group of the secondary cell group has expired and thetransmission on the physical uplink shared channel in the SecondaryTiming Advance Group of the secondary cell group is to be stopped.

Advantageous Effects of Invention

According to the present invention, uplink data can be transmittedefficiently.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating a concept of a radio communicationsystem according to the present embodiment.

FIG. 2 is a diagram illustrating a configuration of a slot according tothe present embodiment.

FIG. 3 is a diagram illustrating an example of special fields foractivation of Semi-Persistent Scheduling according to the presentembodiment.

FIG. 4 is a diagram illustrating an example of special fields forrelease of the Semi-Persistent Scheduling according to the presentembodiment.

FIG. 5 is a diagram for describing examples of non-empty transmissionand empty transmission according to the present embodiment.

FIG. 6 is a diagram illustrating an example of an uplink datatransmission method according to the present embodiment.

FIG. 7 is a diagram illustrating another example of the uplink datatransmission method according to the present embodiment.

FIG. 8 is a diagram illustrating another example of the uplink datatransmission method according to the present embodiment.

FIG. 9 is a diagram illustrating another example of the uplink datatransmission method according to the present embodiment.

FIG. 10 is a diagram illustrating another example of the uplink datatransmission method according to the present embodiment.

FIG. 11 is a diagram illustrating another example of the uplink datatransmission method according to the present embodiment.

FIG. 12 is a schematic block diagram illustrating a configuration of aterminal device 1 according to the present embodiment.

FIG. 13 is a schematic block diagram illustrating a configuration of abase station device 3 according to the present embodiment.

DESCRIPTION OF EMBODIMENTS

Embodiments of the present invention will be described below.

FIG. 1 is a conceptual diagram of a radio communication system accordingto the present embodiment. In FIG. 1, the radio communication systemincludes terminal devices 1A to 1C and a base station device 3.Hereinafter, the terminal devices 1A to 1C are each also referred to asa terminal device 1.

Physical channels and physical signals according to the presentembodiment will be described.

With respect to FIG. 1, the following uplink physical channels are usedfor uplink radio communication from the terminal device 1 to the basestation device 3. Here, the uplink physical channels are used totransmit information output from the higher layers.

-   -   Physical Uplink Control CHannel (PUCCH)    -   Physical Uplink Shared CHannel (PUSCH)    -   Physical Random Access CHannel (PRACH)

The PUCCH is used for transmission of Uplink Control Information (UCI).Here, the uplink control information may include Channel StateInformation (CSI) used to indicate a downlink channel state. The uplinkcontrol information may include Scheduling Request (SR) used to requestan UL-SCH resource. The uplink control information may include HybridAutomatic Repeat reQuest ACKnowledgment (HARQ-ACK). HARQ-ACK mayindicate HARQ-ACK for downlink data (Transport block, Medium AccessControl Protocol Data Unit (MAC PDU), Downlink-Shared CHannel (DL-SCH),or Physical Downlink Shared CHannel (PDSCH)).

In other words, HARQ-ACK may indicate ACKnowledgment (ACK) orNegative-ACKnowledgment (NACK). Here, HARQ-ACK may also be referred toas ACK/NACK, HARQ feedback, HARQ acknowledgment, HARQ information, orHARQ control information.

The PUSCH is used for transmission of uplink data (UpLink-Shared Channel(UL-SCH)). Furthermore, the PUSCH may be used to transmit HARQ-ACKand/or CSI along with the uplink data. Furthermore, the PUSCH may beused to transmit CSI only or HARQ-ACK and CSI only. In other words, thePUSCH may be used to transmit the uplink control information only.

Here, the base station device 3 and the terminal device 1 exchange(transmit and/or receive) signals with each other in their respectivehigher layers. For example, the base station device 3 and the terminaldevice 1 may transmit and receive, in a Radio Resource Control layer,RRC signaling (also referred to as Radio Resource Control message (RRCmessage) or Radio Resource Control information (RRC information)) to andfrom each other. The base station device 3 and the terminal device 1 maytransmit and receive a Medium Access Control (MAC) control element in aMAC layer, respectively. Here, the RRC signaling and/or the MAC controlelement is also referred to as higher layer signaling.

The PUSCH may be used to transmit the RRC signaling and the MAC controlelement. Here, the RRC signaling transmitted from the base stationdevice 3 may be signaling common to multiple terminal devices 1 in acell. The RRC signaling transmitted from the base station device 3 maybe signaling dedicated to a certain terminal device 1 (also referred toas dedicated signaling).

In other words, user-equipment-specific information (information uniqueto user equipment) may be transmitted through signaling dedicated to thecertain terminal device 1.

The PRACH is used to transmit a random access preamble. The PRACH may beused for an initial connection establishment procedure, a handoverprocedure, a connection re-establishment procedure, uplink transmissionsynchronization (timing adjustment), and designating a PUSCH resourcerequest.

In FIG. 1, the following uplink physical signal is used in the uplinkradio communication. Here, the uplink physical signal is not used totransmit information output from the higher layers but is used by thephysical layer.

-   -   UpLink Reference Signal (UL RS)

According to the present embodiment, the following two types of uplinkreference signals are used.

-   -   DeModulation Reference Signal (DMRS)    -   Sounding Reference Signal (SRS)

The DMRS is associated with transmission of the PUSCH or the PUCCH. TheDMRS is time-multiplexed with the PUSCH or the PUCCH. The base stationdevice 3 uses the DMRS in order to perform channel compensation of thePUSCH or the PUCCH. Transmission of both of the PUSCH and the DMRS ishereinafter referred to simply as transmission of the PUSCH.Transmission of both of the PUCCH and the DMRS is hereinafter referredto simply as transmission of the PUCCH.

The SRS is not associated with the transmission of the PUSCH or thePUCCH. The base station device 3 uses the SRS in order to measure anuplink channel state.

In FIG. 1, the following downlink physical channels are used fordownlink radio communication from the base station device 3 to theterminal device 1. Here, the downlink physical channels are used totransmit the information output from the higher layers.

-   -   Physical Broadcast CHannel (PBCH)    -   Physical Control Format Indicator CHannel (PCFICH)    -   Physical Hybrid automatic repeat request Indicator CHannel        (PHICH)    -   Physical Downlink Control CHannel (PDCCH)    -   Enhanced Physical Downlink Control CHannel (EPDCCH)    -   Physical Downlink Shared CHannel (PDSCH)    -   Physical Multicast CHannel (PMCH)

The PBCH is used for broadcasting a Master Information Block (MIB), or aBroadcast CHannel (BCH), that is shared by the terminal devices 1.

The PCFICH is used for transmission of information indicating a region(OFDM symbols) to be used for transmission of the PDCCH.

The PHICH is used for transmission of a HARQ indicator (HARQ feedback orresponse information) indicating an ACKnowledgement (ACK) or a NegativeACKnowledgement (NACK) for the uplink data (UpLink Shared CHannel(UL-SCH)) received by the base station device 3.

The PDCCH and the EPDCCH are used for transmission of Downlink ControlInformation (DCI). Here, multiple DCI formats are defined fortransmission of the downlink control information. In other words, afield for the downlink control information is defined in a DCI formatand is mapped to information bits.

For example, DCI formats for downlink (e.g., DCI format 1, DCI format 1Aand/or DCI format 1C) to be used for the scheduling of one PDSCH in onecell (transmission of a single downlink transport block) may be defined.

Here, each of the downlink DCI formats includes information of thescheduling of the PDSCH. For example, the downlink DCI format includesdownlink control information such as a Carrier Indicator Field (CIF),information of a HARQ process number, information of a Modulation andCoding Scheme (MCS), information of a Redundancy version, and/orinformation of Resource block assignment. Here, the downlink DCI formatis also referred to as downlink grant and/or downlink assignment.

Furthermore, for example, DCI formats for uplink (e.g., DCI format 0 andDCI format 4) to be used for the scheduling of one PUSCH in one cell(transmission of a single uplink transport block) are defined.

Here, each of the uplink DCI formats includes information of thescheduling of the PUSCH. For example, the uplink DCI format includesdownlink control information such as a Carrier Indicator Field (CIF),information of a Transmit Power Command (TPC command) for a scheduledPUSCH, information of cyclic shift DMRS, information of a Modulation andCoding Scheme (MCS) and/or redundancy version, and/or, information ofResource block assignment and/or hopping resource allocation. Here, theuplink DCI format is also referred to as uplink grant and/or Uplinkassignment.

In a case that a PDSCH resource is scheduled in accordance with thedownlink assignment, the terminal device 1 may receive downlink data onthe scheduled PDSCH. In a case that a PUSCH resource is scheduled inaccordance with the uplink grant, the terminal device 1 may transmituplink data and/or uplink control information of the scheduled PUSCH.

Here, the terminal device 1 may monitor a set of PDCCH candidates and/orEPDCCH candidates. The PDCCH may indicate a PDCCH and/or an EPDDCHbelow. Here, the PDCCH candidates are candidates which the PDCCH may bemapped to and/or transmitted on by the base station device 3.Furthermore “monitor” may imply that the terminal device 1 attempts todecode each PDCCH in the set of PDCCH candidates in accordance with eachof all the monitored DCI formats.

The set of PDCCH candidates to be monitored by the terminal device 1 isalso referred to as a search space. The search space may include aCommon Search Space (CSS). For example, the CSS may be defined as aspace common to multiple terminal devices 1. The search space mayinclude an eUE-specific Search Space (USS). For example, the USS may bedefined at least based on a C-RNTI assigned to the terminal device 1.The terminal device 1 may monitor the PDCCHs in the CSS and/or USS todetect a PDCCH destined for the terminal device 1 itself.

Here, an RNTI assigned to the terminal device 1 by the base stationdevice 3 is used for the transmission of the downlink controlinformation (transmission on the PDCCH). Specifically, Cyclic Redundancycheck (CRC) parity bits are appended to the DCI format (or downlinkcontrol information), and after the appending, the CRC parity bits arescrambled with the RNTI. Here, the CRC parity bits appended to the DCIformat may be obtained from a payload of the DCI format.

The terminal device 1 attempts to decode the DCI format to which the CRCparity bits scrambled with the RNTI are attached, and detects, as a DCIformat destined for the terminal device 1 itself, the DCI format forwhich the CRC has been successful (also referred to as blind coding). Inother words, the terminal device 1 may detect the PDCCH with the CRCscrambled with the RNTI. The terminal device 1 may detect the PDCCHincluding the DCI format to which the CRC parity bits scrambled with theRNTI are attached.

Here, the RNTI may include a Cell-Radio Network Temporary Identifier(C-RNTI). The C-RNTI is an identifier unique to the terminal device 1and used for the identification in RRC connection and scheduling. TheC-RNTI may be used for dynamically scheduled unicast transmission.

The RNTI may further include a Semi-Persistent Scheduling C-RNTI (SPSC-RNTI). The SPS C-RNTI is an identifier unique to the terminal device 1and used for semi-persistent scheduling. The SPS C-RNTI may be used forsemi-persistently scheduled unicast transmission.

Here, the semi-persistently scheduled transmission includes meaning ofperiodically scheduled transmission. For example, the SPS C-RNTI may beused for activation, reactivation, and/or re-transmission of thesemi-persistently scheduled transmission. Hereinafter, the activationmay include meaning of the reactivation and/or the re-transmission.

The SPS C-RNTI may be used for release and/or deactivation of thesemi-persistently scheduled transmission. Hereinafter, the release mayinclude meaning of the deactivation. Here, an RNTI may be newly definedfor the latency reduction. For example, the SPS C-RNTI in the presentembodiment may include an RNTI newly defined for the latency reduction.

The RNTI may include a Random Access RNTI (RA-RNTI). The RA-RNTI is anidentifier used for transmission of a random access response message. Inother words, the RA-RNTI is used for the transmission of the randomaccess response message in a random access procedure. For example, theterminal device 1 may monitor the PDCCH with the CRC scrambled with theRA-RNTI after the transmission of a random access preamble. The terminaldevice 1 may receive a random access response on the PDSCH in accordancewith detection of the PDCCH with the CRC scrambled with the RA-RNTI.

The RNTI may further include a Paging RNTI (P-RNTI). The P-RNTI is anidentifier used for paging and notification of system informationmodification. For example, the P-RNTI is used for paging andtransmission of a system information message. For example, the terminaldevice 1 may receive paging on the PDSCH in accordance with detection ofthe PDCCH with the CRC scrambled with the P-RNTI.

The RNTI may further include a System Information RNTI (SI-RNTI). TheSI-RNTI is an identifier used for broadcast of the system information.For example, the SI-RNTI is used for transmission of the systeminformation message. For example, the terminal device 1 may receive thesystem information message on the PDSCH in accordance with detection ofthe PDCCH with the CRC scrambled with the SI-RNTI.

Here, for example, the PDCCH with the CRC scrambled with the C-RNTI maybe transmitted in the USS or CSS. The PDCCH with the CRC scrambled withthe RA-RNTI may be transmitted only in the CSS. The PDCCH with the CRCscrambled with the P-RNTI may be transmitted only in the CSS. The PDCCHwith the CRC scrambled with the SI-RNTI may be transmitted only in theCSS.

The PDCCH with the CRC scrambled with the SPS C-RNTI may be transmittedonly in a primary cell and primary secondary cell. The PDCCH with theCRC scrambled with the SPS C-RNTI may be transmitted in the USS or CSS.

The PDSCH is used for transmission of downlink data (DownLink SharedCHannel (DL-SCH)). The PDSCH is used to transmit a system informationmessage. Here, the system information message may be cell-specificinformation (information unique to a cell). The system information isincluded in RRC signaling. The PDSCH is used to transmit the RRCsignaling and the MAC control element.

The PMCH is used for transmission of multicast data (Multicast CHannel(MCH)).

In FIG. 1, the following downlink physical signals are used for downlinkradio communication. Here, the downlink physical signals are not used totransmit the information output from the higher layers but is used bythe physical layer.

-   -   Synchronization Signal (SS)    -   DownLink Reference Signal (DL RS)

The synchronization signal is used for the terminal device 1 to besynchronized to frequency and time domains in the downlink. In the TDDscheme, the synchronization signal is mapped to subframes 0, 1, 5, and 6within a radio frame. In the FDD scheme, the Synchronization signal ismapped to subframes 0 and 5 within a radio frame.

The downlink reference signal is used for the terminal device 1 toperform channel compensation on a downlink physical channel. Thedownlink reference signal is used in order for the terminal device 1 toobtain the downlink channel state information.

According to the present embodiment, the following five types ofdownlink reference signals are used.

-   -   Cell-specific Reference Signal (CRS)    -   UE-specific Reference Signal (URS) associated with the PDSCH    -   DeModulation Reference Signal (DMRS) associated with the EPDCCH    -   Non-Zero Power Channel State Information-Reference Signal (NZP        CSI-RS)    -   Zero Power Channel State Information-Reference Signal (ZP        CSI-RS)    -   Multimedia Broadcast and Multicast Service over Single Frequency        Network Reference Signal (MBSFN RS)    -   Positioning Reference Signal (PRS)

Here, the downlink physical channel and the downlink physical signal arecollectively referred to as a downlink signal. The uplink physicalchannel and the uplink physical signal are collectively referred to asan uplink signal. The downlink physical channels and the uplink physicalchannels are collectively referred to as physical channels. The downlinkphysical signals and the uplink physical signals are collectivelyreferred to as physical signals.

The BCH, the MCH, the UL-SCH, and the DL-SCH are transport channels. Achannel used in the Medium Access Control (MAC) layer is referred to asa transport channel. A unit of the transport channel used in the MAClayer is also referred to as a Transport Block (TB) or a MAC ProtocolData Unit (PDU). A Hybrid Automatic Repeat reQuest (HARQ) is controlledfor each transport block in the MAC layer. The transport block is a unitof data that the MAC layer delivers to the physical layer. In thephysical layer, the transport block is mapped to a codeword andsubjected to coding processing on a codeword-by-codeword basis.

Now, carrier aggregation will be described.

In the present embodiment, one or multiple serving cells may beconfigured for the terminal device 1. A technology in which the terminaldevice 1 communicates via the multiple serving cells is referred to ascell aggregation or carrier aggregation.

Here, the present embodiment may apply to one or each of the multipleserving cells configured for the terminal device 1. Alternatively, thepresent embodiment may apply to one or some of the multiple servingcells configured for the terminal device 1. Alternatively, the presentembodiment may apply to one or each of the multiple serving cell groupsconfigured for the terminal device 1.

In the present embodiment, Time Division Duplex (TDD) and/or FrequencyDivision Duplex (FDD) may be applied. Here, for the carrier aggregation,TDD or FDD may apply to one or all of the multiple serving cells.Alternatively, for the carrier aggregation, serving cells to which TDDapplies and serving cells to which FDD applies may be aggregated. Here,a frame structure for FDD is also referred to as Frame structure type 1.A frame structure for TDD is also referred to as Frame structure type 2.

Here, one or multiple configured serving cells may include one primarycell and one or multiple secondary cells. For example, the primary cellmay be a serving cell in which an initial connection establishmentprocedure has been performed, a serving cell in which a connectionre-establishment procedure has been initiated, or a cell designated asthe primary cell by a handover procedure. Here, upon an RRC connectionbeing established or later, a secondary cell(s) may be configured.

Here, a carrier corresponding to a serving cell in the downlink isreferred to as a downlink component carrier. A carrier corresponding toa serving cell in the uplink is referred to as an uplink componentcarrier. The downlink component carrier and the uplink component carrierare collectively referred to as a component carrier.

The terminal device 1 may simultaneously perform transmission and/orreception on multiple physical channels in one or multiple serving cells(component carrier(s)). Here, transmission of one physical channel maybe performed in one serving cell (component carrier) of the multipleserving cells (component carriers).

Here, the transmission on the PUCCH may be performed only in the primarycell. The primary cell cannot be deactivated. Cross-carrier schedulingdoes not apply to the primary cell. In other words, the primary cell isalways scheduled via its PDCCH.

The secondary cell is activated and/or deactivated. In a case that PDCCH(or PDCCH monitoring) of a certain secondary cell is configured,cross-carries scheduling may not apply this secondary cell. To be morespecific, in this case, the secondary cell may always be scheduled viaits PDCCH. In a case that no PDCCH (or PDCCH monitoring) of a certainsecondary cell is configured, cross-carrier scheduling applies to thesecondary cell, and the secondary cell may always be scheduled via thePDCCH of one other serving cell.

A configuration of a slot according to the present embodiment will bedescribed below.

FIG. 2 is a diagram illustrating the configuration of the slot accordingto the present embodiment. In FIG. 2, a horizontal axis represents atime axis, and a vertical axis represents a frequency axis. Here, anormal Cyclic Prefix (CP) may apply to an OFDM symbol. Alternatively, anextended Cyclic Prefix (CP) may apply to the OFDM symbol. The physicalsignal or physical channel transmitted in each of the slots is expressedby a resource grid.

Here, in the downlink, the resource grid may be defined with multiplesubcarriers and multiple OFDM symbols. In the uplink, the resource gridmay be defined with multiple subcarriers and multiple SC-FDMA symbols.The number of subcarriers constituting one slot may depend on a cellbandwidth. The number of OFDM symbols or SC-FDMA symbols constitutingone slot may be seven. Here, each element within the resource grid isreferred to as a resource element. The resource element may beidentified by a subcarrier number and an OFDM symbol or SC-FDMA symbolnumber.

Here, a resource block may be used to express mapping of a certainphysical channel (PDSCH, PUSCH, or the like) to resource elements. Forthe resource block, a virtual resource block and a physical resourceblock may be defined. A certain physical channel may be first mapped tothe virtual resource block. Thereafter, the virtual resource block maybe mapped to the physical resource block. One physical resource blockmay be defined with seven consecutive OFDM symbols or SC-FDMA symbols inthe time domain and 12 consecutive subcarriers in the frequency domain.Thus, one physical resource block may include (7×12) resource elements.Furthermore, one physical resource block may correspond to one slot inthe time domain and correspond to 180 kHz in the frequency domain. Thephysical resource blocks may be numbered from zero in the frequencydomain.

Here, in the present embodiment, basically, the Semi-PersistentScheduling (SPS) is described as a scheduling method for transmittingthe uplink data, but the scheduling described in the present embodimentis not limited to the Semi-Persistent Scheduling. To be more specific,the scheduling method described in the present embodiment is notnecessarily to be called the Semi-Persistent Scheduling. In other words,the uplink data transmission method described in the present embodimentis not limited to the uplink data transmission method based on theSemi-Persistent Scheduling, but, of course, the present embodimentincludes those similar to the uplink data transmission method describedin the present embodiment.

In the present embodiment, for the description of the processing in theterminal device 1, described are processing of the MAC entity in theterminal device 1, a “Multiplexing and assembly” entity in the terminaldevice 1 (hereinafter, also referred to as a first entity), and/or anHARQ entity in the terminal device 1. In other words, the presentembodiment describes the processing of the MAC entity in the terminaldevice 1, the first entity in the terminal device 1, and/or the HARQentity in the terminal device 1, but, of course, the processing in thepresent embodiment is the processing in the terminal device 1.

The present embodiment basically describes behavior (processing) of theterminal device 1, but, of course, the base station device 3 performssimilar behavior (processing) correspondingly to the behavior(processing) of the terminal device 1.

Here, the transmission on the PUSCH (which may be transmission on theUL-SCH) is performed at a timing based on a System Frame Number (SFN)and the subframe. To be more specific, in order to specify the timingfor the transmission on the PUSCH, the SFN and a subframe number/indexin the radio frame corresponding to the SFN are needed. Here, the SFN isa number/index of a radio frame.

Hereinafter, for the purpose of simple description, the SFN (radioframe) and subframe transmitted on the PUSCH are also simply describedas the subframe. In other words, the subframe in the followingdescription may include meanings of the SFN (radio frame) and subframe.

Here, the base station device 3 may configure an interval (period) ofthe uplink Semi-Persistent Scheduling for the terminal device 1. Forexample, the base station device 3 may transmit a first parameter and/orsecond parameter for indicating a value of the interval of the uplinkSemi-Persistent Scheduling to the terminal device 1 by including theparameters in higher layer signaling (RRC message).

For example, the base station device 3 may use the first parameterand/or second parameter to configure the interval value of theSemi-Persistent Scheduling as 10 (10 subframes), 20 (20 subframes), 32(32 subframes), 40 (40 subframes), 64 (64 subframes), 80 (80 subframes),128 (128 subframes), 160 (160 subframes), 320 (320 subframes), and/or640 (640 subframes).

The base station device 3 may use the first parameter and/or secondparameter to configure the interval value of the Semi-PersistentScheduling as 1 (1 subframe), 10 (10 subframes), 20 (20 subframes), 32(32 subframes), 40 (40 subframes), 64 (64 subframes), 80 (80 subframes),128 (128 subframes), 160 (160 subframes), 320 (320 subframes), and/or640 (640 subframes).

To be more specific, the base station device 3 may use the firstparameter and/or second parameter to configure the interval value of theSemi-Persistent Scheduling as 1 (1 subframe).

For example, the first parameter and/or the second parameter may beconfigured for each serving cell. The first parameter may be configuredfor the primary cell. The second parameter may be configured for theprimary cell and/or the secondary cell (may be configured for eachserving cell). The interval value of the Semi-Persistent Scheduling, “1(1 subframe)”, may be configured for the primary cell and/or thesecondary cell (may be configured for each serving cell).

The base station device 3 may use the uplink DCI format (e.g., DCIformat 0) to allocate a semi-persistent (semi-permanent, semi-persistentor periodical) PUSCH resource (physical resource block) to the terminaldevice 1, and instruct the terminal device 1 to activate thetransmission on the semi-persistent PUSCH. The base station device 3 mayuse the uplink DCI format to instruct the terminal device 1 to releasethe semi-persistent PUSCH resource.

For example, in a case that CRC parity bits attached to the DCI formatare scrambled with the SPS C-RNTI, and a field of information of a NewData Indicator included within the DCI format is set to ‘0’, theterminal device 1 may verify (confirm, or check) whether multipleinformation fields included within the DCI format are set to specificvalues. To be more specific, the CRC parity bits attached to the DCIformat scrambled with the SPS C-RNTI, and the field of the informationof the New Data Indicator may be used for validation of theSemi-Persistent Scheduling.

Here, in a case that the verification is succeeded, the terminal device1 may consider (recognize) that the received DCI format indicates avalid semi-persistent activation or a valid semi-persistent release. Ina case that the verification is not succeeded, the terminal device 1 maydiscard (clear) this DCI format.

Here, the semi-persistent activation may include meaning of activationof the Semi-Persistent Scheduling. The semi-persistent activation mayalso include meaning of semi-persistent allocation of the PUSCHresource. The semi-persistent release may include meaning of release ofthe Semi-Persistent Scheduling.

To be more specific, the DCI format may be used to indicate theactivation of semi-persistent uplink scheduling. The DCI format may beused to enable activation of the Semi-Persistent Scheduling. The DCIformat may be used to indicate the semi-persistent release.

FIG. 3 is a diagram illustrating an example of Special fields foractivation of the Semi-Persistent Scheduling. As illustrated in FIG. 3,multiple fields may be defined for activation of the Semi-PersistentScheduling. A predetermined value (that may be a specific value) set ineach of multiple fields may be defined for activation of theSemi-Persistent Scheduling.

As illustrated in FIG. 3, for example, in a case that the uplink DCIformat (e.g., DCI format 0) is used for activation of theSemi-Persistent Scheduling, a field of information of the TPC commandfor the scheduled PUSCH included within the uplink DCI format may be setto ‘00’, a field of information of the Cyclic shift DMRS may be set to‘000’, and the Most Significant Bit (MSB) of a field of information ofthe Modulation and Coding Scheme (MCS) and redundancy version may be setto ‘0’.

For example, in a case that the downlink DCI format (e.g., DCI format 1and/or DCI format 1A) is used for activation of the Semi-PersistentScheduling, a field of information of a HARQ process number includedwithin the downlink DCI format may be set to ‘000 (for FDD)’ or ‘0000(for TDD)’, the Most Significant Bit (MSB) of a field of information ofthe Modulation and Coding scheme (MCS) may be set to ‘0’, and a field ofinformation of the redundancy version may be set to ‘00’.

In other words, in a case that each of multiple information fieldsincluded within the DCI format is set to a specific value defined inadvance, the terminal device 1 may activate the Semi-PersistentScheduling. Here, multiple information fields and predetermined valuesto which the information fields are set which are used for activation ofthe Semi-Persistent Scheduling are not limited to the examples describedabove, of course. For example, multiple information fields andpredetermined values to which the information fields are set which areused for activation of the Semi-Persistent Scheduling may be defined byspecifications or the like in advance to be used as information known toboth the base station device 3 and the terminal device 1.

FIG. 4 is a diagram illustrating an example of Special fields forrelease of the Semi-Persistent Scheduling. As illustrated in FIG. 4,multiple fields may be defined for release of the Semi-PersistentScheduling. A predetermined value (that may be a specific value) set ineach of multiple fields may be defined for release of theSemi-Persistent Scheduling.

As illustrated in FIG. 4, for example, in a case that the uplink DCIformat (e.g., DCI format 0) is used for release of the Semi-PersistentScheduling, the field of the information of the TPC command for thescheduled PUSCH included within the uplink DCI format may be set to‘00’, the field of the information of the Cyclic shift DMRS may be setto ‘000’, the field of the information of the Modulation and CodingScheme (MCS) and redundancy version may be set to ‘11111’, and a fieldof information of Resource block assignment and hopping resourceallocation (that may be all fields of multiple fields) may be set to‘1’.

In other words, in a case that the uplink DCI format is used for releaseof the Semi-Persistent Scheduling, the field associated with theresource block assignment (resource allocation) may be set to a valuedefined in advance for release.

For example, in a case that the downlink DCI format (e.g., DCI format 1and/or DCI format 1A) is used for release of the Semi-PersistentScheduling, the field of the information of the HARQ process numberincluded within the downlink DCI format may be set to ‘000 (for FDD)’ or‘0000 (for TDD)’, the field of the information of the Modulation andCoding Scheme (MCS) may be set to ‘11111’, the field of the informationof the redundancy version may be set to ‘00’, and the field of theinformation of the Resource block assignment (that may be all fields ofmultiple fields) may be set to ‘1’.

In other words, in a case that the downlink DCI format is used forrelease of the Semi-Persistent Scheduling, the field associated with theresource block assignment (resource allocation) may be set to a valuedefined in advance for release.

In other words, in the case that each of multiple information fieldsincluded within the DCI format is set to a specific value defined inadvance, the terminal device 1 may release the Semi-PersistentScheduling. Here, multiple information fields and predetermined valuesto which the information fields are set which are used for release ofthe Semi-Persistent Scheduling are not limited to the examples describedabove, of course. For example, multiple information fields andpredetermined values to which the information fields are set which areused for release of the Semi-Persistent Scheduling may be defined byspecification or the like in advance to be used as information known toboth the base station device 3 and the terminal device 1.

Here, the Semi-Persistent Scheduling may be supported only in theprimary cell and the primary secondary cell. To be more specific, theDCI format to which the CRC parity bits scrambled with the SPS C-RNTIare attached may be transmitted only for the primary cell and theprimary secondary cell. The DCI format to which the CRC parity bitsscrambled with the C-RNTI are attached may be transmitted for theprimary cell, the primary secondary cell, and/or the secondary cell(s).

For example, the DCI format to which the CRC parity bits scrambled withthe SPS C-RNTI are attached may be transmitted for the secondary cell ina case that the interval value of the Semi-Persistent Scheduling as “1(1 subframe)” is configured for the secondary cell.

Here, the terminal device 1 has to have a valid uplink grant forperforming the transmission on the UL-SCH (transmission on the UL-SCHvia the PUSCH, and/or UL-SCH transmission on the PUSCH). Here, theuplink grant may include meaning that uplink transmission in a certainsubframe is granted (permitted, or given).

For example, the valid uplink grant may be dynamically received on thePDCCH. To be more specific, the valid uplink grant may be indicatedusing the DCI format to which the CRC parity bits scrambled with theC-RNTI are attached. The valid uplink grant may be semi-permanentlyconfigured. To be more specific, the valid uplink grant may be indicatedusing the DCI format to which the CRC parity bits scrambled with the SPSC-RNTI are attached.

The terminal device 1 may store the uplink grant dynamically received onthe PDCCH and/or the semi-permanently configured uplink grant. Here, theHARQ entity may deliver the uplink grant dynamically received on thePDCCH and/or the semi-permanently configured uplink grant to a HARQprocess, and the HARQ process may store the uplink grant received fromthe HARQ entity.

Hereinafter, the uplink grant dynamically received on the PDCCH and/orsemi-permanently configured uplink grant which are to be stored arereferred to as a stored uplink grant.

In the case of being instructed to perform the semi-persistentactivation, the terminal device 1 (MAC entity) may store the DCI formatreceived from the base station device 3 as a configured uplink grant.Here, the configured uplink grant may be referred to as a configuredSemi-Persistent Scheduling UpLink grant (SPS UL grant), or a configuredgrant. The configured uplink grant may be referred to as a configureduplink grant, a configured Semi-Persistent Scheduling UpLink grant (SPSUL grant), or a configured grant.

Here, based on that the UpLink grant (SPS UL grant) stored by the MACentity is cleared, the UpLink grant (SPS UL grant) stored by the HARQprocess may not be cleared. To be more specific, even in a case that theUpLink grant (SPS UL grant) stored by the MAC entity is cleared,re-transmission on the semi-persistent PUSCH can be continued based onthe UpLink grant (SPS UL grant) stored by the HARQ process.

The Semi-Persistent Scheduling uplink grant may be referred to as a SPSuplink grant, a Semi-Persistent grant, and a Semi-persistent schedulingassignment.

The base station device 3 may configure validation and/or invalidationof the Semi-Persistent Scheduling for the terminal device 1. Forexample, the base station device 3 may configure validation and/orinvalidation of the Semi-Persistent Scheduling by using higher layersignaling (e.g., RRC layer signaling).

In a case that the Semi-Persistent Scheduling is validated, the SPSC-RNTI, a parameter for indicating the interval value of the uplinkSemi-Persistent Scheduling, a parameter for indicating the Number ofempty transmissions before release (also referred to as a thirdparameter), and/or a SPS deactivation timer (also referred to as afourth parameter) may be at least provided (configured). Here, the emptytransmission (also referred to as transmission of empty) is describedlater. The third parameter and the fourth parameter are described later.

Here, for example, the terminal device 1 starts transmission of acertain subframe on the semi-persistent PUSCH, and then, may initializeor reinitialize the configured uplink grant such that the transmissionon the semi-persistent PUSCH recurs based on Equation (1). To be morespecific, the terminal device 1 may sequentially consider that theconfigured uplink grant occurs in a subframe satisfying Equation (1).

(10*SFN+subframe)=[(10*SFN_(start_time)+subframe_(start_time))+N*semiPersistSchedIntervalUL+Subframe_Offset*(Nmodulo2)]modulo10240  [Equation 1]

In other words, the terminal device 1, after configuring the SPS uplinkgrant, may set a value of Subframe_Offset, and recognize (considersequentially) that the N-th grant (configured uplink grant, SPS uplinkgrant) occurs in the subframe specified based on Equation (1).

Here, the subframe satisfying Equation (1) is also referred to as asubframe satisfying a predetermined condition. The subframes among thesubframes satisfying Equation (1) except for the first subframe are alsoreferred to as subframes satisfying a predetermined condition. Here, thefirst subframe among the subframe satisfying Equation (1) may be areceived subframe of the DCI which is used to indicate the activation orreactivation or release of the Semi-Persistent Scheduling.

Specifically, the terminal device 1 may specify the subframe for thetransmission on the PUSCH corresponding to the N-th configured uplinkgrant, based on Equation (1), after configuring the stored DCI format asthe SPS uplink grant. Here, in Equation (1), SFN and subframe representthe SFN and subframe, respectively, transmitted on the PUSCH.

In Equation (1), SFNstart-time and subframestart-time represent the SFNand subframe, respectively, at the time the configured uplink grant areinitialized or reinitialized. To be more specific, SFNstart-time andsubframestart-time represent, the SFN and subframe starting thetransmission on the PUSCH, based on the configured uplink grant (i.e.,the subframe for an initial transmission on the PUSCH corresponding tothe 0-th configured uplink grant).

In Equation (1), semiPersistSchedIntervalUL represents the interval ofthe uplink Semi-Persistent Scheduling. In Equation (1), Subframe_Offsetrepresents an offset value used to specify the subframe for thetransmission on the PUSCH.

Here, the terminal device 1 may set Subframe_Offset in Equation (1) to‘0’ in a case that a parameter (twoIntervalConfig) is not validated byhigher layer after configuring the SPS uplink grant.

The initialization may be performed in a case that the Semi-PersistentScheduling is not activated. The reinitialization may be performed in acase that the Semi-Persistent Scheduling is already activated. Here, theinitialization may include meaning of initial configuration, and thereinitialization may include meaning of re-initial configuration. Inother words, the terminal device 1 may initialize or reinitialize theconfigured uplink grant to start the transmission on the PUSCH in acertain subframe.

FIG. 5 is a diagram for describing examples of Non-empty transmissionand Empty transmission. As illustrated in FIG. 5, a MAC Protocol DataUnit (MAC PDU) may be constituted by a MAC header, a MAC Service DataUnit (MAC SDU), a MAC Control Element (MAC CE), and padding (paddingbits). Here, the MAC protocol data unit may correspond to the uplinkdata (UL-SCH).

Here, there may be defined, as the MAC control element, multiple MACcontrol elements including at least a Buffer Status Report MAC controlelement (Buffer Status Report MAC CE, BSR MAC CE, which is a MAC controlelement used for buffer status report), a Timing Advance Command MACcontrol element (Timing Advance Command MAC CE, TAC MAC CE, which is aMAC control element used to transmit a timing advance command), a PowerHeadroom Report MAC control element (Power Headroom Report MAC CE, PHRMAC CE, which is a MAC control element used for power headroom report),and/or an Activation/Deactivation MAC control element(Activation/Deactivation MAC CE, which is a MAC control element used totransmit an activation/deactivation command).

There may be defined, as the buffer status report, multiple bufferstatus reports including at least a Regular BSR, a Periodic BSR, and apadding BSR. For example, the Regular BSR, the Periodic BSR, and thepadding BSR may be triggered based on events (conditions) different fromeach other.

For example, the Regular BSR may be triggered in a case that data for alogical channel which belongs to a certain Logical Channel Group (LCG)becomes available for transmission, and priority for the transmission ofthe data is higher than the logical channels which belong to any LCG andfor which data is already available for transmission, or in a case thatthere is no available data for transmission on the logical channelswhich belong to any LCG. The Regular BSR may also be triggered in a casethat a predetermined timer (retxBSR-Timer) expires, and the terminaldevice 1 has available data for transmission for the logical channelswhich belong to a certain LCG.

The Periodic BSR may be triggered in a case that a prescribed timer(periodic BSR-Timer) expires. The padding BSR may be triggered in a casethat the UL-SCH is allocated, and the number of padding bits is equal toor larger than a size of the Buffer Status Report MAC control elementplus its subheader.

The terminal device 1 may use the buffer status report to notify thebase station device 3 of a transmission data buffer size of the uplinkdata corresponding to each LCG as a message in the MAC layer.

As illustrated in FIG. 5, the MAC protocol data unit may contain zero,one, or multiple MAC service data units. The MAC protocol data unit maycontain zero, one, or multiple MAC control elements. Padding may occurat the end of the MAC Protocol Data Unit (MAC PDU).

Here, the non-empty transmission may be transmission of the MAC protocoldata unit including one or multiple MAC service data units (or maycorrespond to transmission of MAC protocol data unit including at leastone or multiple MAC service data units).

The non-empty transmission may be transmission of the MAC protocol dataunit including one or multiple first MAC control elements (or maycorrespond to transmission of the MAC protocol data unit including atleast one or multiple first MAC control elements). Here, the first MACcontrol element (or a first predetermined MAC control element) may bedefined in advance by specifications or the like, and may be informationknown to both the base station device 3 and the terminal device 1.

For example, the first MAC control element may contain one or all of themultiple MAC control elements described above. For example, the firstMAC control element may be a Buffer Status Report MAC control element.The first MAC control element may be a Power Headroom Report MAC controlelement.

For example, the first MAC control element may be a Buffer Status ReportMAC control element including a Regular BSR. The first MAC controlelement may be a Buffer Status Report MAC control element including aPeriodic BSR. The first MAC control element may be a Buffer StatusReport MAC control including a padding BSR.

To be more specific, the non-empty transmission may be transmission ofthe MAC protocol data unit including one or multiple MAC service dataunits and/or one or multiple first MAC control elements (or maycorrespond to transmission of the MAC protocol data unit including atleast one or multiple MAC service data units and/or one or multiplefirst MAC control elements).

The empty transmission may be transmission of the MAC protocol data unitincluding only padding (or may correspond to transmission of the MACprotocol data unit including only padding). Here, the MAC header isappended to the transmission of the MAC protocol data unit includingonly padding.

The empty transmission may be transmission of the MAC protocol data unitincluding one or multiple second MAC control elements (or may correspondto transmission of the MAC protocol data unit including at least one ormultiple second MAC control elements). Here, the second MAC controlelement (or a second predetermined MAC control element) may be definedin advance by specifications or the like, and may be information knownto both the base station device 3 and the terminal device 1.

Here, the second MAC control element may be a MAC control element otherthan the first MAC control element. For example, the second MAC controlelement may contain one or all of the multiple MAC control elementsdescribed above. For example, the second MAC control element may be aBuffer Status Report MAC control element. The second MAC control elementmay be a Power Headroom Report MAC control element.

For example, the second MAC control element may be a Buffer StatusReport MAC control element including a Regular BSR. The second MACcontrol element may be a Buffer Status Report MAC control elementincluding a Periodic BSR. The second MAC control element may be a BufferStatus Report MAC control including a padding BSR.

To be more specific, the empty transmission may be transmission of theMAC protocol data unit including padding and/or only one or multiplesecond MAC control elements (or may correspond to transmission of theMAC protocol data unit including only padding and/or one or multiplesecond MAC control elements).

Here, the non-empty transmission and/or the empty transmission may betransmission corresponding to a new transmission. To be more specific,transmitting, in the new transmission, the MAC protocol data unitincluding at least one or multiple MAC service data units and/or one ormultiple first MAC control elements may be referred to as the non-emptytransmission. Transmitting, in the new transmission, the MAC protocoldata unit including only padding and/or one or multiple second MACcontrol elements may be referred to as the empty transmission.

The non-empty transmission and/or the empty transmission may beperformed on the PUSCH scheduled by the base station device 3. Forexample, the non-empty transmission and/or the empty transmission may beperformed on the PUSCH scheduled by using the DCI (DCI format) to whichthe CRC parity bits scrambled with the C-RNTI are attached (i.e.,dynamically scheduled PUSCH resource). The non-empty transmission and/orthe empty transmission may be performed on the PUSCH scheduled by usingthe DCI (DCI format) to which the CRC parity bits scrambled with the SPSC-RNTI are attached (i.e., semi-permanently scheduled PUSCH resource).

As described above, the terminal device 1 may semi-permanently(semi-persistently or periodically) perform the transmission on thePUSCH (transmission on the UL-SCH) in the subframe specified based onEquation (1). Here, the terminal device 1 may clear the configured grantbased on the third parameter (parameter for indicating the Number ofempty transmissions before release) configured by the base stationdevice 3.

For example, the terminal device 1 may clear the configured grant in acase that the number of consecutive empty transmissions corresponding tothe initial transmission on the semi-persistent PUSCH reaches a valueindicated by using the third parameter (the number of transmissions).

To be more specific, the terminal device 1 may clear the configuredgrant immediately after the third parameter corresponding to the numberof consecutive new MAC Protocol Data Units (PDUs) each of which containsno MAC service data unit (i.e., each of which contains zero MAC SDUs).Here, the number of the consecutive empty transmissions corresponding tothe initial transmission include the number of empty transmissions onthe Semi-Persistent Scheduling resource. Here, the number of theconsecutive empty transmissions corresponding to the initialtransmission does not include the number of empty transmissions on thedynamically scheduled PUSCH resource.

Here, the terminal device 1 may release (clear) the uplink resourceallocated by the base station device 3 (Semi-Persistent Schedulingresource, PUSCH resource), based on the third parameter. Specifically,the terminal device 1 may release the uplink resource allocated by thebase station device 3 similarly to clearing the configured grant, basedon the third parameter. Here, the terminal device 1, in a case ofreceiving the DCI format which is used to indicate the release of theSemi-Persistent Scheduling described above, may clear the configuredgrant and/or release the uplink resource.

Hereinafter, a first behavior refers to a behavior in which the terminaldevice 1 transmits the uplink data, and clears the configured grantand/or releases the uplink resource, based on the third parameter asdescribed above. The first behavior also refers to a behavior in whichthe terminal device 1 transmits the uplink data, and clears theconfigured grant and/or releases the uplink resource in the case ofreceiving the DCI format which is used to indicate the release of theSemi-Persistent Scheduling as described above.

Here, in the first behavior, the terminal device 1 immediately clearsthe configured grant and/or releases the uplink resource in the case ofreceiving the DCI format which is used to indicate the release of theSemi-Persistent Scheduling. To be more specific, the terminal device 1immediately clears the configured grant and/or releases the uplinkresource without transmitting any information to the base station 3 inthe case of receiving the DCI format which is used to indicate therelease of the Semi-Persistent Scheduling.

FIG. 6 a diagram for describing a method for clearing the configuredgrant in the first action. Here, FIG. 6 illustrates an action in thecase that the interval value of the Semi-Persistent Scheduling isconfigured to be “1 (1 subframe)”.

As illustrated in FIG. 6, the terminal device 1 may receive the DCIwhich is used to indicate the activation and/or reactivation of theSemi-Persistent Scheduling. The terminal device 1 may perform thenon-empty transmission on the Semi-Persistent Scheduling resource. To bemore specific, the terminal device 1 may perform the non-emptytransmission based on the configured uplink grant according to Equation(1) described above. The terminal device 1 may perform the emptytransmission on the Semi-Persistent Scheduling resource. To be morespecific, the terminal device 1 may perform the empty transmission onthe Semi-Persistent Scheduling resource in the case of no available datafor transmission.

Here, the terminal device 1 may clear the configured grant in a casethat the number of consecutive empty transmissions on theSemi-Persistent Scheduling resource reaches the value configured byusing the third parameter (the number of transmissions). The terminaldevice 1 may release the uplink resource (Semi-Persistent Schedulingresource) in the case that the number of consecutive empty transmissionson the Semi-Persistent Scheduling resource reaches the value configuredby using the third parameter (the number of transmissions).Specifically, the terminal device 1 may clear the configured grantand/or release the uplink resource, based on the third parameter.

FIG. 7 is a diagram for describing an uplink data transmission methodaccording to the present embodiment. The uplink data transmission methoddescribed with reference to FIG. 7 may be applied to the base stationdevice 3 and/or terminal device 1 described above. Hereinafter, abehavior described with reference to FIG. 7 is also referred to as asecond behavior. FIG. 7 illustrates a behavior in the case that theinterval value of the Semi-Persistent Scheduling is configured to be “1(1 subframe)”. The transmission illustrated in FIG. 7 represents thetransmission on the Semi-Persistent Scheduling resource.

As illustrated in FIG. 7, the base station device 3 may transmit thefourth parameter to the terminal device 1. For example, the base stationdevice 3 may transmit the fourth parameter by using higher layersignaling (e.g., RRC layer signaling). For example, the fourth parametermay include a parameter used to configure to perform the second behavior(which may be a partial behavior included in the second behavior). Thefourth parameter may include a parameter used to configure the intervalvalue of the uplink Semi-Persistent Scheduling “1 (1 subframe)”.

The fourth parameter may include a parameter used to configure a firsttimer (also referred to as a SPS deactivation timer) described later.The fourth parameter may include a parameter used to configure a secondtimer (also referred to as a SPS prohibit timer) described later. Thefourth parameter may include a parameter used to configure a subframefor which the transmission corresponding to the Semi-PersistentScheduling is not performed (that is, a subframe for which thetransmission corresponding to the Semi-Persistent Scheduling is notpermitted to be performed) described later.

The fourth parameter may include a parameter used to configure whetherthe empty transmission is performed on the Semi-Persistent Schedulingresource (configure to perform or not to perform the transmission).

To be more specific, the terminal device 1 may switch between the firstbehavior and the second behavior, based on the fourth parametertransmitted by the base station device 3 (e.g., a parameter in thehigher layer or a parameter in the RRC layer). For example, the terminaldevice 1 may perform the first behavior in a case of not beingconfigured with the fourth parameter, and perform the second behavior ina case of being configured with the fourth parameter.

In a subframe n, the terminal device 1 receives the DCI (the DCI format,the uplink grant) which is used to indicate the activation and/orreactivation of the Semi-Persistent Scheduling. Here, the terminaldevice 1 may perform the non-empty transmission or the emptytransmission in a subframe corresponding to the subframe in which theDCI used to indicate the activation and/or reactivation of theSemi-Persistent Scheduling is received (e.g., a subframe 4 subframesafter the subframe n, that is, a subframe n1).

Specifically, in the subframe n1, the terminal device 1 having availabledata for transmission may perform the non-empty transmission. Here, in acase that the terminal device 1 is given an uplink grant size that isequal to or larger than predetermined bytes (e.g., 4 bytes) and hasavailable data for transmission, the terminal device 1 may perform thenon-empty transmission. In other words, for example, the terminal device1 having available data for transmission in the subframe n1 does notperform the transmission of only the padding BSR and/or padding.

In the subframe n1, the terminal device 1 not having available data fortransmission may perform the empty transmission. Here, in a case thatthe terminal device 1 is given a DCI format (e.g., uplink grant) thesize of which is smaller than predetermined bytes (e.g., 7 bytes) anddoes not have available data for transmission, the terminal device 1 mayperform the empty transmission.

A subframe n2 represents a subframe in which the terminal device 1 doesnot have available data for transmission. Here, in the subframe n2, theterminal device 1 not having available data for transmission does notperform the empty transmission.

In other words, the terminal device 1 configured with the fourthparameter does not perform the empty transmission in a case of nothaving available data for transmission. As described above, the terminaldevice 1 not configured with the fourth parameter performs the emptytransmission in the case of not having available data for transmission.To be more specific, the terminal device 1 may switch between whether toperform the empty transmission, based on the fourth parameter, in thecase of not having available data for transmission.

Here, in the subframe n2, the terminal device 1 may always perform thenon-empty transmission or the empty transmission in a case oftransmission corresponding to the DCI (the DCI format, the uplink grant)to which the CRC parity bits scrambled with the C-RNTI are attached. Inother words, in a case that a PUSCH resource is scheduled by using theDCI to which the CRC parity bits scrambled with the C-RNTI are attached,the terminal device 1 may always perform the non-empty transmission orthe empty transmission on the scheduled

PUSCH resource.

To be more specific, a resource scheduled by using the DCI to which theCRC parity bits scrambled with the C-RNTI are attached (dynamicallyscheduled resource) may override a resource scheduled by using the DCIto which the CRC parity bits scrambled with the SPS C-RNTI are attached(semi-permanently scheduled resource).

Here, the scheduled PUSCH resource may be a resource of a serving cellincluding the Semi-Persistent Scheduling resource. The scheduled PUSCHresource may be a resource of a serving cell other than the serving cellincluding the Semi-Persistent Scheduling resource. Specifically, thescheduled PUSCH resource may be a resource of a serving cell includingthe Semi-Persistent Scheduling resource, or a resource of a serving cellother than the serving cell including the Semi-Persistent Schedulingresource.

Specifically, the terminal device 1 which is configured with the fourthparameter, has the available data for transmission, and is given theuplink grant corresponding to the Semi-Persistent Scheduling may performthe non-empty transmission. Here, the terminal device 1 may perform thenon-empty transmission only in a case that the size of the uplink grantcorresponding to the Semi-Persistent Scheduling is equal to or largerthan predetermined bytes (e.g., 4 bytes).

The terminal device 1 which is configured with the fourth parameter,does not have the available data for transmission, and is given theuplink grant corresponding to the Semi-Persistent Scheduling does notperform the empty transmission. Here, the terminal device 1 may notperform the empty transmission only in a case that the size of theuplink grant corresponding to the Semi-Persistent Scheduling is smallerthan predetermined bytes (e.g., 7 bytes).

The terminal device 1 which has the available data for transmission andis given the uplink grant corresponding to the dynamic scheduling mayperform the non-empty transmission regardless of being configured withthe fourth parameter. Here, the terminal device 1 may perform thenon-empty transmission only in a case that the size of the uplink grantcorresponding to the dynamic scheduling is equal to or larger thanpredetermined bytes (e.g., 4 bytes).

The terminal device 1 which does not have the available data fortransmission and is given the uplink grant corresponding to the dynamicscheduling may perform the empty transmission regardless of beingconfigured with the fourth parameter. Here, the terminal device 1 mayperform the empty transmission only in the case that the size of theuplink grant corresponding to the dynamic scheduling is smaller thanpredetermined bytes (e.g., 7 bytes).

Each of a subframe n3, a subframe n4, and a subframe n5 represents asubframe in which the terminal device 1 has available data fortransmission. In the subframe n3, subframe n4, and subframe n5, theterminal device 1 having available data for transmission may perform thenon-empty transmission.

In a subframe n6, the terminal device 1 receives the DCI (the DCIformat, the uplink grant) which is used to indicate the release of theSemi-Persistent Scheduling. Here, the terminal device 1 may perform thenon-empty transmission or the empty transmission in a subframecorresponding to the subframe in which the DCI used to indicate therelease of the Semi-Persistent Scheduling is received (e.g., a subframe4 subframes after the subframe n6, that is, a subframe n7).

Here, the terminal device 1 may perform the non-empty transmission orthe empty transmission on the PUSCH (PUSCH resource) scheduled using themost recent DCI which is used to indicate the activation and/ordeactivation of the Semi-Persistent Scheduling in the case of receivingthe DCI which is used to indicate the release of the Semi-PersistentScheduling. In other words, the terminal device 1 may perform thenon-empty transmission or the empty transmission on the PUSCH (PUSCHresource) scheduled by using the configured grant which is stored.

As described above, the field associated with the resource blockassignment (resource allocation) in the DCI which is used to indicatethat the release of the Semi-Persistent Scheduling may be set to a valuedefined in advance for the release of the Semi-Persistent Scheduling.Therefore, the terminal device 1 may perform the non-empty transmissionor the empty transmission, based on the configured grant in the case ofreceiving the DCI which is used to indicate the release of theSemi-Persistent Scheduling.

To be more specific, in the subframe n7, the terminal device 1 havingavailable data for transmission may perform the non-empty transmissionbased on the configured grant. Here, in the case that the terminaldevice 1 is given an uplink grant size that is equal to or larger thanpredetermined bytes (e.g., 4 bytes) and has available data fortransmission, the terminal device 1 may perform the non-emptytransmission based on the configured grant. In other words, for example,in the subframe n7, the terminal device 1 having available data fortransmission does not perform the transmission of only the padding BSRand/or padding.

In the subframe n7, the terminal device 1 not having available data fortransmission may perform the empty transmission based on the configuredgrant. Here, in the case that the terminal device 1 is given a DCIformat (e.g., uplink grant) the size of which is smaller thanpredetermined bytes (e.g., 7 bytes) and does not have available data fortransmission, the terminal device 1 may perform the empty transmissionbased on the configured grant.

The terminal device 1 may clear the configured grant and/or release theuplink resource in a subframe in which the non-empty transmission orempty transmission is performed or in subframes after the subframe. Thatis, the terminal device 1 configured with the fourth parameter mayperform the non-empty transmission or empty transmission in the case ofreceiving the DCI which is used to indicate the release of theSemi-Persistent Scheduling, and may clear the configured grant and/orrelease the uplink resource in a subframe in which the non-emptytransmission or empty transmission is performed or in subframes afterthe subframe.

The terminal device 1 may clear the configured grant and/or release theuplink resource in subframe in which the DCI used to indicate therelease of the Semi-Persistent Scheduling is received or in subframesafter the subframe. That is, the terminal device 1 configured with thefourth parameter, in the case of receiving the DCI which is used toindicate the release of the Semi-Persistent Scheduling, may deliver theconfigured grant to the HARQ entity, and thereafter, may clear theconfigured grant and/or release the uplink resource in a subframe inwhich the DCI used to indicate the release of the Semi-PersistentScheduling is received or in subframes after the subframe.

As describe above, the terminal device 1 not configured with the fourthparameter clears the configured grant and/or releases the uplinkresource without transmitting any information to the base station 3 inthe case of receiving the DCI which is used to indicate the release ofthe Semi-Persistent Scheduling. That is, the terminal device 1 mayperform the non-empty transmission or empty transmission in the case ofreceiving the DCI which is used to indicate the release of theSemi-Persistent Scheduling, based on the fourth parameter, andthereafter, may switch between whether to clear the configured grantand/or release the uplink resource, or to clear the configured grantand/or release the uplink resource without transmitting any informationto the base station 3.

As described above, the terminal device 1 not having available data fortransmission does not perform the empty transmission. To be morespecific, not performing the empty transmission may be defined as thebehavior (processing) in the HARQ entity in the terminal device 1. Inother words, performing the non-empty transmission, not performing thenon-empty transmission, performing the empty transmission, and/or notperforming the empty transmission may be defined as the behavior(processing) in the HARQ entity.

For example, it may be defined that after the HARQ entity obtains theMAC Protocol Data Unit (MAC PDU) to transmit from the first entity, theHARQ process is not instructed to trigger the new transmission (aninitial transmission) (the initial transmission is not triggered).

Specifically, the first entity may provide the MAC protocol data unit totransmit. A Logical Channel Prioritization procedure in a case that thenew transmission is performed may be applied to the first entity. Thefirst entity may multiplex the MAC control elements and the MAC servicedata units.

Not performing the empty transmission may be defined as the behavior(processing) in the HARQ process in the terminal device 1. In otherwords, performing the non-empty transmission, not performing thenon-empty transmission, performing the empty transmission, and/or notperforming the empty transmission may be defined as the behavior(processing) in the HARQ process.

For example, it may be defined that the HARQ process does not instruct aphysical layer to generate the transmission according to the storeduplink grant.

Not performing the empty transmission may be defined as the behavior(processing) in the first entity. In other words, performing thenon-empty transmission, not performing the non-empty transmission,performing the empty transmission, and/or not performing the emptytransmission may be defined as the behavior (processing) in the firstentity. Here, the behavior (processing) in the first entity may be thebehavior (processing) of the MAC entity in a procedure relating to“Multiplexing and assembly”.

Here, the first entity, in a case of having available data fortransmission, may generate the MAC protocol data unit including the MACservice data unit. The first entity, in a case of not having availabledata for transmission, may generate the MAC protocol data unit notincluding the MAC service data unit.

The first entity, in a case that the Regular BSR is triggered, maygenerate the MAC protocol data unit including the Buffer Status ReportMAC CE including the Regular BSR. The first entity, in a case that thePeriodic BSR is triggered, may generate the MAC protocol data unitincluding the Buffer Status Report MAC CE including the Periodic BSR.

In a case that the empty transmission is not performed, the first entitymay not generate the MAC protocol data unit corresponding to the emptytransmission. In the case that the empty transmission is not performed,the first entity may not deliver the MAC protocol data unitcorresponding to the empty transmission to the HARQ entity.

Here, in the case that the empty transmission is not performed, the HARQentity may not deliver the MAC protocol data unit corresponding to theempty transmission to the HARQ process. In the case that the emptytransmission is not performed, the HARQ process may not deliver the MACprotocol data unit corresponding to the empty transmission to thephysical layer.

For example, it may be defined that in a case the MAC entity isconfigured with the fourth parameter, has available data fortransmission, and given the uplink grant corresponding to theSemi-Persistent Scheduling, the MAC entity transmits the MAC protocoldata unit including one or multiple MAC service data units. Here, asdescribed above, the MAC entity may transmit the MAC protocol data unitonly in the case that the size of the uplink grant corresponding to theSemi-Persistent Scheduling is equal to or larger than predeterminedbytes (e.g., 4 bytes).

It may be also defined that in the case the MAC entity is configuredwith the fourth parameter, has available data for transmission, and isgiven the uplink grant corresponding to the Semi-Persistent Scheduling,the MAC entity transmits the MAC protocol data unit including one ormultiple first MAC control elements. Here, as described above, the MACentity may transmit the MAC protocol data unit only in the case that thesize of the uplink grant corresponding to the Semi-Persistent Schedulingis equal to or larger than predetermined bytes (e.g., 4 bytes).

That is, it may be defined that in the case the MAC entity is configuredwith the fourth parameter, has available data for transmission, and isgiven the uplink grant corresponding to the Semi-Persistent Scheduling,the MAC entity transmits the MAC protocol data unit including one ormultiple MAC service data units and/or one or multiple first MAC controlelements.

It may be defined that in the case the MAC entity is configured with thefourth parameter, has available data for transmission, and is given theuplink grant corresponding to the Semi-Persistent Scheduling, the MACentity does not transmit the MAC protocol data unit including onlypadding. Here, as described above, the MAC entity may transmit the MACprotocol data unit in the case that the size of the uplink grantcorresponding to the Semi-Persistent Scheduling is smaller thanpredetermined bytes (e.g., 7 bytes).

It may be defined that in the case the MAC entity is configured with thefourth parameter, has available data for transmission, and is given theuplink grant corresponding to the Semi-Persistent Scheduling, the MACentity does not transmit the MAC protocol data unit including one ormultiple second MAC control elements. Here, as described above, the MACentity may transmit the MAC protocol data unit in the case that the sizeof the uplink grant corresponding to the Semi-Persistent Scheduling issmaller than predetermined bytes (e.g., 7 bytes).

It may be defined that in the case the MAC entity is configured with thefourth parameter, has available data for transmission, and is given theuplink grant corresponding to the Semi-Persistent Scheduling, the MACentity does not transmit the MAC protocol data unit including onlypadding and/or one or multiple second MAC control elements.

The base station device 3 may transmit a parameter used to configure anuplink subframe for which the transmission corresponding to theSemi-Persistent Scheduling is not performed (that is, an uplink subframefor which the transmission corresponding to the Semi-PersistentScheduling is not permitted to be performed). For example, the basestation device 3 may transmit the parameter used to configure an uplinksubframe for which the transmission corresponding to the Semi-PersistentScheduling is not performed, by using higher layer signaling (RRC layersignaling).

For example, the uplink subframe for which the transmissioncorresponding to the Semi-Persistent Scheduling is not performed may beconfigured by use of a bitmap method, where an uplink subframe for whichthe transmission corresponding to the Semi-Persistent Scheduling ispermitted to be performed may be expressed by “0”, and an uplinksubframe for which the transmission corresponding to the Semi-PersistentScheduling is not permitted to be performed may be expressed by “1”.

The terminal device 1 dose not perform uplink transmission in the uplinksubframe for which the transmission corresponding to the Semi-PersistentScheduling is not permitted to be performed. To be more specific, evenin a case that the terminal device 1 has available data for transmission(even in a case that the non-empty transmission occurs), the terminaldevice 1 does not perform the uplink transmission in the uplink subframefor which the transmission corresponding to the Semi-PersistentScheduling is not permitted to be performed. In other words, theterminal device 1 may perform uplink transmission only in an uplinksubframe for which the transmission corresponding to the Semi-PersistentScheduling is permitted to be performed.

FIG. 8 is a diagram for describing an uplink data transmission methodaccording to the present embodiment. The uplink data transmission methoddescribed with reference to FIG. 8 may be applied to the base stationdevice 3 and/or terminal device 1 described above. Here, a behaviordescribed with reference to FIG. 8 is included in the second behavior.As described above, the terminal device 1 may switch between the firstbehavior and the second behavior, based on the fourth parametertransmitted by the base station device 3.

FIG. 8 illustrates that the terminal device 1 receives, in a subframe n8and a subframe n10, the DCI (the DCI format, the uplink grant) which isused to indicate the activation and/or reactivation of theSemi-Persistent Scheduling on the PDCCH. FIG. 8 also illustrates thatthe terminal device 1 receives, in a subframe n9, predeterminedinformation of the PDCCH (predetermined PDCCH).

Here, as illustrated in FIG. 8, the terminal device 1 may start thefirst timer (also referred to as the SPS deactivation timer), based onthe reception of the DCI which is used to indicate the activation and/orreactivation of the Semi-Persistent Scheduling in the subframe n. To bemore specific, the terminal device 1 may start the first timer in asubframe in which the DCI used to indicate the activation and/orreactivation of the Semi-Persistent Scheduling is received or insubframes after the subframe.

The terminal device 1 may start the first timer in a subframe in whichtransmission corresponding to the DCI used to indicate the activationand/or reactivation of the Semi-Persistent Scheduling is performed or insubframes after the subframe. For example, the terminal device 1 mayperform the non-empty transmission or empty transmission in a subframecorresponding to the subframe in which the DCI used to indicate theactivation and/or reactivation of the Semi-Persistent Scheduling isreceived (e.g., a subframe that is 4 subframes after the subframe n8),and may start the first timer in a subframe in which the non-emptytransmission or empty transmission is performed or in subframes afterthe subframe.

The base station device 3 may transmit a parameter used to configure thefirst timer (a first timer value) to the terminal device 1. For example,the base station device may transmit the parameter used to configure thefirst timer (the first timer value) by using higher layer signaling(e.g., RRC layer signaling). The terminal device 1 may set the firsttimer (the first timer value), based on the parameter transmitted by thebase station device 3.

The terminal device 1 may restart the first timer based on the receptionof predetermined information in the subframe n9. For example, theterminal device 1 may restart the first timer in a subframe in which thepredetermined information is received or in subframes after thesubframe. Here, the terminal device 1 may restart the first timer in asubframe in which transmission corresponding to the predeterminedinformation is performed or in subframes after the subframe. Theterminal device 1 may restart the first timer in a subframe in whichreception corresponding to the predetermined information is performed orin subframes after the subframe.

Here, whether to restart the first timer depending on what type of thepredetermined information the terminal device 1 receives in the subframen9 may be defined in advance by specifications or the like, and theinformation may be known to both the base station device 3 and theterminal device 1.

For example, the predetermined information may satisfy some or all of(i) to (vii) below. (i) The predetermined information may be the DCI forprimary cell.

(ii) The predetermined information may be the DCI for secondary cell.

(iii) The predetermined information may be the downlink DCI format (theDCI for downlink, the downlink assignment).

(iv) The predetermined information may be the uplink DCI format (the DCIfor the uplink, the uplink grant).

(v) The predetermined information may be the DCI to which the CRC paritybits scrambled with the C-RNTI are attached.

(vi) The predetermined information may be the DCI to which the CRCparity bits scrambled with the SPS C-RNTI are attached.

(vii) The predetermined information may be the DCI to which the CRCparity bits scrambled with any one of the SI-RNTI, RA-RNTI, and P-RNTIare attached.

Here, for example, the predetermined information satisfying above (i),(iv), and (v) may be the DCI for the uplink for the primary cell towhich the CRC parity bits scrambled with the C-RNTI are attached.

The terminal device 1 may restart the first timer, based on thereception of the DCI which is used to indicate the activation and/orreactivation of the Semi-Persistent Scheduling in the subframe n10. Forexample, the terminal device 1 may restart the first timer in a subframein which the DCI used to indicate the activation and/or reactivation ofthe Semi-Persistent Scheduling is received or in subframes after thesubframe.

The terminal device 1 may restart the first timer in a subframe in whichthe transmission corresponding to the DCI used to indicate theactivation and/or reactivation of the Semi-Persistent Scheduling (e.g.,non-empty transmission or empty transmission) is performed or insubframes after the subframe.

A subframe n11 represents a subframe in which the first timer expires.The terminal device 1 may clear the configured grant in a case that thefirst timer expires. The terminal device 1 may release (clear) theuplink resource allocated by the base station device 3 (Semi-PersistentScheduling resource, PUSCH resource) in the case that the first timerexpires. The terminal device 1 may stop the first timer in the case thatthe first timer expires.

To be more specific, the terminal device 1 may maintain the first timer,and deactivate the associated transmissions, based on the expiration ofthe first timer. In other words, the first timer may be used todeactivate the transmission corresponding to the Semi-PersistentScheduling. Specifically, the terminal device 1 may perform thenon-empty transmission on the Semi-Persistent Scheduling resource whilethe first timer is running. The terminal device 1 does not perform theempty transmission on the Semi-Persistent Scheduling resource (alsoreferred to as a second empty transmission) while the first timer isrunning.

Here, the first timer may be indicated as a counter. For example, thefirst timer may be indicated as a counter for the number of times ofoccurrences of the configured grant (the number of occurrences of theconfigured grant).

Specifically, the terminal device 1 may clear the configured grant in acase that the counter (the first timer) reaches a predetermined value.The terminal device 1 may release (clear) the uplink resource allocatedby the base station device 3 (Semi-Persistent Scheduling resource, PUSCHresource) in the case that that the counter (the first timer) reaches apredetermined value. Specifically, a parameter used to configure thepredetermined value may be configured by the base station device 3.

To be more specific, the terminal device 1 may restart the counter (thefirst timer), based on the reception of the predetermined information inthe subframe n9. For example, the terminal device 1 may reset thecounter (the first timer) in a subframe in which the predeterminedinformation is received or in subframes after the subframe. Here, theterminal device 1 may reset the counter (the first timer) in a subframein which the transmission corresponding to the predetermined informationis performed or in subframes after the subframe. The terminal device 1may reset the counter (the first timer) in a subframe in which thereception corresponding to the predetermined information is performed orin subframes after the subframe.

The terminal device 1 may reset the counter (the first timer), based onthe reception of the DCI which is used to indicate the activation and/orreactivation of the Semi-Persistent Scheduling in the subframe n10. Forexample, the terminal device 1 may reset the counter (the first timer)in a subframe in which the DCI used to indicate the activation and/orreactivation of the Semi-Persistent Scheduling is received or insubframes after the subframe.

The terminal device 1 may reset the counter (the first timer) in asubframe in which the transmission corresponding to the DCI used toindicate the activation and/or reactivation of the Semi-PersistentScheduling (e.g., non-empty transmission or empty transmission) isperformed or in subframes after the subframe.

As described above, the terminal device 1 not configured with the fourthparameter may clear the configured grant and/or release the uplinkresource, based on the third parameter (parameter for indicating theNumber of empty transmissions before release). The terminal device 1configured with the fourth parameter may clear the configured grantand/or release the uplink resource, based on the first timer (SPSdeactivation timer).

That is, the terminal device 1 may switch between whether to clear theconfigured grant and/or release the uplink resource according to thethird parameter, or to clear the configured grant and/or release theuplink resource according to the parameter used to configure the firsttimer, based on whether being configured with the fourth parameter.

FIG. 9 is a diagram for describing an uplink data transmission methodaccording to the present embodiment. The uplink data transmission methoddescribed with reference to FIG. 9 may be applied to the base stationdevice 3 and/or terminal device 1 described above. Here, a behaviordescribed with reference to FIG. 9 is included in the second behavior.As described above, the terminal device 1 may switch between the firstbehavior and the second behavior, based on the fourth parametertransmitted by the base station device 3.

FIG. 9 illustrates that the terminal device 1 receives, in a subframen12 and a subframe n15, the DCI (the DCI format, the uplink grant) whichis used to indicate the activation and/or reactivation of theSemi-Persistent Scheduling on the PDCCH. FIG. 9 also illustrates thatthe terminal device 1 receives, in a subframe n18, predeterminedinformation of the PDCCH (predetermined PDCCH). FIG. 9 also illustratesthat the terminal device 1 receives, in a subframe n19, the DCI which isused to indicate the release of the Semi-Persistent Scheduling (the DCIformat, the uplink grant) on the PDCCH.

Here, the predetermined information in FIG. 9 may be different from thepredetermined information in FIG. 8.

Here, each of a subframe n13 and a subframe n16 represents a subframe inwhich the empty transmission occurs. As described above, the terminaldevice 1 does not perform the empty transmission in the subframe n13. Asubframe n14 represents a subframe in which the non-empty transmissionoccurs. As described above, the terminal device 1 performs the non-emptytransmission in the subframe n14.

Here, the terminal device 1 performing the non-empty transmission in thesubframe n14 may start the second timer (also referred to as the SPSprohibit timer). In other words, the terminal device 1 may start thesecond timer in a subframe in which the non-empty transmission isperformed or in subframes after the subframe. The terminal device 1 maymaintain the second timer, and prohibit (stop) associated transmissionswhile the second timer is running. In other words, the second timer maybe used to prohibit the transmission corresponding to theSemi-Persistent Scheduling. Here, the second timer may not prohibit thetransmission corresponding to the dynamically scheduled resource.

Here, the base station device 3 may transmit a parameter used toconfigure the second timer (a second timer value) to the terminal device1. For example, the base station device may transmit the parameter usedto configure the second timer (the second timer value) by using higherlayer signaling (e.g., RRC layer signaling). The terminal device 1 mayset the second timer (the second timer value), based on the parametertransmitted by the base station device 3.

A subframe n17 represents a subframe in which the second timer expires.The terminal device 1 may restart associated transmissions in a casethat the second timer expires. For example, the terminal device 1 mayperform the non-empty transmission.

The terminal device 1 may start the second timer, based on the receptionof predetermined information in the subframe n18. Specifically, theterminal device 1 may start the second timer in a subframe in which theprescribed information is received or in subframes after the subframe.The terminal device 1 may restart the second timer in a subframe inwhich transmission corresponding to the predetermined information isperformed or in subframes after the subframe. The terminal device 1 mayrestart the second timer in a subframe in which reception correspondingto the predetermined information is performed or in subframes after thesubframe.

Here, whether to restart the second timer depending on what type of thepredetermined information the terminal device 1 receives in the subframen18 may be defined in advance by specifications or the like, and theinformation may be known to both the base station device 3 and theterminal device 1.

For example, the predetermined information may satisfy some or all of(i) to (vii) described above. (i) The predetermined information may bethe DCI for primary cell.

(ii) The predetermined information may be the DCI for secondary cell.

(iii) The predetermined information may be the downlink DCI format (theDCI for downlink, the downlink assignment).

(iv) The predetermined information may be the uplink DCI format (the DCIfor the uplink, the uplink grant).

(v) The predetermined information may be the DCI to which the CRC paritybits scrambled with the C-RNTI are attached.

(vi) The predetermined information may be the DCI to which the CRCparity bits scrambled with the SPS C-RNTI are attached.

(vii) The predetermined information may be the DCI to which the CRCparity bits scrambled with any one of the SI-RNTI, RA-RNTI, and P-RNTIare attached.

Here, for example, the predetermined information satisfying above (i),(iv), and (v) may be the DCI for the uplink for the primary cell towhich the CRC parity bits scrambled with the C-RNTI are attached.

As described above, the terminal device 1 receiving the DCI which isused to indicate the activation and/or reactivation of theSemi-Persistent Scheduling in the subframe n12 and subframe n15 mayperform the non-empty transmission or the empty transmission incorresponding subframes (e.g., a subframe 4 subframes after the subframen12 (subframe n13), and a subframe 4 subframes after the subframe n15(subframe n16)).

Here, the terminal device 1 may not start the second timer in a case ofperforming the empty transmission in the corresponding subframe. Theterminal device 1 may start the second timer in a case of performing thenon-empty transmission in the corresponding subframe. Specifically, theterminal device 1 may switch between whether to start the second timer,based on which of the empty transmission and the non-empty transmissionis performed in the case of receiving the DCI which is used to indicatethe activation and/or reactivation of the Semi-Persistent Scheduling.

The terminal device 1 may start the second timer in a case of performingthe non-empty transmission or the empty transmission in thecorresponding subframe. Specifically, the terminal device 1 may alwaysstart the second timer in the case of performing the empty transmissionor the non-empty transmission depending on the DCI which is used toindicate the activation and/or reactivation of the Semi-PersistentScheduling.

Here, as is described as the behavior in the subframe n16, the terminaldevice 1 may perform the empty transmission or the non-emptytransmission depending on the DCI which is used to indicate theactivation and/or reactivation of the Semi-Persistent Scheduling, evenwhile the second timer is running. The terminal device 1 may perform theempty transmission or the non-empty transmission depending on the DCIwhich is used to indicate the activation and/or reactivation of theSemi-Persistent Scheduling, and restart the second timer, even while thesecond timer is running.

The terminal device 1 receiving the DCI which is used to indicate therelease of the Semi-Persistent Scheduling in the subframe n19 mayperform the non-empty transmission or the empty transmission incorresponding subframes (e.g., a subframe 4 subframes after the subframen19 (subframe n20)).

Here, as is described as the action in the subframe n16, the terminaldevice 1 may perform the empty transmission or the non-emptytransmission depending on the DCI which is used to indicate the releaseof the Semi-Persistent Scheduling, even while the second timer isrunning. The terminal device 1 may perform the empty transmission or thenon-empty transmission depending on the DCI which is used to indicatethe release of the Semi-Persistent Scheduling, and stop the secondtimer, even while the second timer is running.

Here, the terminal device 1 may stop the first timer as well as stop thesecond timer. For example, the terminal device 1 may perform the emptytransmission or the non-empty transmission depending on the DCI which isused to indicate the release of the Semi-Persistent Scheduling, and stopthe first timer and stop the second timer, even while the second timeris running.

FIG. 10 is a diagram for describing an uplink data transmission methodaccording to the present embodiment. The uplink data transmission methoddescribed with reference to FIG. 10 may be applied to the base stationdevice 3 and/or terminal device 1 described above. Here, a behaviordescribed with reference to FIG. 10 is included in the second behavior.As described above, the terminal device 1 may switch between the firstbehavior and the second behavior based on the fourth parametertransmitted by the base station device 3.

FIG. 10 illustrates an action in a case that a subframe bundlingoperation is configured for the terminal device 1 performing the secondbehavior. Here, the base station device 3 may use a parameter in thehigher layer (also referred to as ttiBundling) to configure the subframebundling operation. For example, in a case that the parameter in thehigher layer is used to configure usage of the subframe bundling, thesubframe bundling operation may be applied to only the UL-SCH. To bemore specific, four consecutive uplink subframes may be used for thetransmission on the UL-SCH (uplink data transmission). Here, fourconsecutive uplink subframes may be referred to as a bundle.

As illustrated in FIG. 10, for example, the terminal device 1 configuredwith the subframe bundling operation may perform the non-emptytransmission in a subframe n21. The terminal device 1 may also performre-transmission corresponding to the non-empty transmission in asubframe n22, a subframe n23, and a subframe n24. Here, the subframen21, subframe n22, subframe n23, and subframe n24 represent the fourconsecutive uplink subframes.

Here, the terminal device 1 configured with the subframe bundlingoperation may start the first timer after performing the non-emptytransmission in the subframe n21. The terminal device 1 configured withthe subframe bundling operation may start the second timer afterperforming the non-empty transmission in the subframe n21.

Specifically, the terminal device 1 may start the first timer after thetransmission in the first uplink subframe among the four consecutiveuplink subframes. The terminal device 1 may start the second timer afterthe transmission in the first uplink subframe among the four consecutiveuplink subframes.

Here, the terminal device 1, even in a case of starting the second timerafter performing the non-empty transmission in the subframe n21, may notbe prohibited from the uplink transmission in the other threeconsecutive uplink subframes. That is, the terminal device 1 configuredwith the subframe bundling operation, even in a case of starting thesecond timer in the first uplink subframe among the four consecutiveuplink subframes, may not be prohibited from the uplink transmission inthe other three consecutive uplink subframes (uplink subframes otherthan the first uplink subframe among the four consecutive subframe).

Here, the terminal device 1 configured with the subframe bundlingoperation may start the first timer after performing re-transmissioncorresponding to the non-empty transmission in the subframe n24. Theterminal device 1 configured with the subframe bundling operation maystart the second timer after performing re-transmission corresponding tothe non-empty transmission in the subframe n24.

Specifically, the terminal device 1 may start the first timer after thetransmission in the last uplink subframe among the four consecutiveuplink subframes. The terminal device 1 may start the second timer afterthe transmission in the last uplink subframe among the four consecutiveuplink subframes.

FIG. 11 is a diagram for describing an uplink data transmission methodaccording to the present embodiment. The uplink data transmission methoddescribed with reference to FIG. 11 may be applied to the base stationdevice 3 and/or terminal device 1 described above.

Here, the base station device 3 may configure a cell group (e.g., amaster cell group and/or a secondary cell group) associated with a dualconnectivity for the terminal device 1. For example, the base stationdevice 3 may use the information (parameter) included in higher layersignaling to configure the cell group associated with the dualconnectivity.

Here, in the dual connectivity, the master cell group may include theprimary cell. In the dual connectivity, the secondary cell group mayinclude the primary secondary cell. Here, for an operation relating tothe dual connectivity, the primary cell of the master cell group and/orthe primary secondary cell of the secondary cell group are also referredto as a special cell.

Here, the special cell (the primary cell of the master cell group and/orprimary secondary cell of the secondary cell group in the dualconnectivity) may be used for the transmission on the PUCCH. Acontention based random access procedure may be performed in the specialcell. To be more specific, the special cell may support the transmissionon the PUCCH, and/or the contention based random access (the contentionbased random access procedure).

In the dual connectivity, the primary cell is not deactivated. In otherwords, the primary cell is always activated. In the dual connectivity,the primary secondary cell is not deactivated. In other words, theprimary secondary cell is always activated.

In the dual connectivity, the terminal device 1 may (simultaneously)connect to a Master eNB (MeNB) and a secondary eNB (SeNB, SecondaryeNB). In a case that the cell group associated with the dualconnectivity is configured, two MAC entities may be configured for theterminal device 1. Here, one of the two MAC entities may indicate a MACentity for the master cell group. The other of the two MAC entities mayindicate a MAC entity for the secondary cell group. In a case that thecell group associated with the dual connectivity is not configured, oneMAC entity may be configured for the terminal device 1.

In other words, in the case that the cell group associated with the dualconnectivity is configured, each of a first MAC entity corresponding tothe master cell group and a second MAC entity corresponding to thesecondary cell group may perform the associated processing in theterminal device 1.

The base station device 3 may configure a cell group associated withTiming Advance (e.g., Primary Timing Advance Group and/or SecondaryTiming Advance Group) for the terminal device 1. For example, the basestation device 3 may use the information (parameter) included in higherlayer signaling to configure the cell group associated with the TimingAdvance. Hereinafter, the cell group associated with the Timing Advanceis also referred to as the Timing Advance Group (TAG).

For example, the same timing reference cell and the same Timing Advance(TA) value may be used for the cell with the configured uplink includedin the same TAG.

Here, the Primary Timing Advance Group (PTAG) is a TAG including theprimary cell. A timing reference cell for the PTAG is the primary cell.A Primary Secondary Timing Advance Group (PSTAG) is a TAG including theprimary secondary cell. A timing reference cell for the PSTAG is theprimary secondary cell.

The Secondary Timing Advance Group (STAG) is a TAG not including theprimary cell, and may contain at least one serving cell with theconfigured uplink. Here, a timing reference cell for the STAG is any oneof the secondary cells included in the STAG.

The base station device 3 may transmit a Timing Advance (TA) command forthe PTAG. The base station device 3 may transmit a TA command for theSTAG. Here, the TA command may be transmitted together with a TAGIdentity which is used to indicate the TAG corresponding to the TAcommand.

The terminal device 1, in a case of receiving the TA command for thePTAG, may adjust the uplink transmission timing on the PUSCH, PUCCH,and/or SRS of the primary cell, based on the received TA command. Here,in a case that the secondary cell belongs to the PTAG, the uplinktransmission timing on the PUSCH, PUCCH and/or SRS of the secondary cellmay be the same as the uplink transmission timing for the primary cell.

The terminal device 1, in a case of receiving the TA command for thePSTAG, may adjust the uplink transmission timing on the PUSCH, PUCCH,and/or SRS of the primary secondary cell, based on the received TAcommand. Here, in a case that the secondary cell belongs to the PSTAG,the uplink transmission timing on the PUSCH, PUCCH and/or SRS of thesecondary cell may be the same as the uplink transmission timing for theprimary secondary cell.

The terminal device 1, in a case of receiving the TA command for theSTAG, may adjust the uplink transmission timings on the PUSCH, PUCCH,and/or SRS of the all secondary cells in the STAG based on the receivedTA command. Here, the uplink transmission timings on the PUSCH, PUCCHand/or SRS may be the same for the all secondary cells in the STAG.

For example, the terminal device 1 may measure a reference timing, basedon a downlink signal of the timing reference cell (e.g., simultaneoussignal). The terminal device 1 may determine the TA for the uplinktransmission, based on the TA command. The terminal device 1 maydetermine the uplink transmission timing, based on the measuredreference timing and determined TA value.

Here, the terminal device 1 may adjust a transmission timing differencebetween the TAGs (PTAG, PSTAG, and/or STAG) to not exceed the maximumtransmission timing difference. Here, for example, the maximumtransmission timing difference may be at least 32.47 μs.

For example, the terminal device 1 may adjust the transmission timingdifference between the TAGs to not exceed the maximum transmissiontiming difference in dual connectivity in which the master cell groupand the secondary cell group are synchronized with each other.

Here, the terminal device 1 may stop adjusting in a case that thetransmission timing difference between the TAGs becomes larger than themaximum transmission timing difference. Here, in a case that thetransmission timing difference between the TAGs becomes larger than themaximum transmission timing difference (exceeds the maximum transmissiontiming difference), the terminal device 1 may consider that a thirdtimer (also referred to as timeAlignmentTimer) as expired and may stopthe uplink transmission.

For example, the base station device 3 may transmit a parameter which isused to configure the third timer. For example, the base station devicemay transmit the parameter used to configure the third timer by usinghigher layer signaling (e.g., RRC layer signaling). Here, the parameterused to configure the third timer may be transmit for each TAG.Specifically, the third timer may be configured for each TAG. To be morespecific, the third timer may be configured for each of the PTAG, PSTAG,and STAG.

For example, the third timer may be used to control how long theterminal device 1 (UE) considers the serving cells belongs to theassociated TAG to be uplink time aligned.

FIG. 11 illustrates a behavior in the dual connectivity in which themaster cell group and the secondary cell group are synchronized witheach other. Here, in the dual connectivity in which the master cellgroup and the secondary cell group are synchronized with each other, adifference between a downlink reception timing in the master cell groupand a downlink reception timing in the secondary cell group may be 33 μsor less.

In FIG. 11, each of (NTA,1+NTAoffset,1)·TS sec, and(NTA,2+NTAoffset,2)·TS sec represents a difference between a downlinkreception timing and uplink transmission timing in the master cellgroup. Each of (NTA,3+NTAoffset,3)·TS sec, and (NTA,4+NTAoffset,4)·TSsec represents a difference between a downlink reception timing anduplink transmission timing in the secondary cell group.

The terminal device 1 may calculate the uplink transmission timingdifference between the TAGs (PTAG, PSTAG, and STAG), based on(NTA,1+NTAoffset,1)·TS sec, (NTA,2+NTAoffset,2)·TS sec,(NTA,3+NTAoffset,3)·TS sec, (NTA,4+NTAoffset,4)·TS sec, and/or 33 μs(that is the difference between the downlink reception timing in themaster cell group and the downlink reception timing in the secondarycell group).

Here, each of NTA,1, NTA,2, NTA,3, and NTA,4 may be a value based on theTA command. Each of NTAoffset,1, NTAoffset,2, NTAoffset,3, andNTAoffset,4 may be a value determined based on whether the serving cellbelonging to corresponding TAG is a TDD serving cell or a FDD servingcell. For example, the NTAoffset value may be “624” for TDD. TheNTAoffset value may be “0” for FDD.

Here, for example, in a case that a difference between the uplinktransmission timing for the PTAG of the master cell group and the uplinktransmission timing for the STAG of the master cell group exceeds themaximum transmission timing difference, the terminal device 1 mayconsider that the third timer for the STAG of the master cell group asexpired to stop the uplink transmission for the STAG of the master cellgroup. Specifically, the terminal device 1 may stop the transmission onthe PUSCH, PUCCH, and/or SRS for the STAG of the master cell group.

In a case that a difference between the uplink transmission timing forthe PTAG of the master cell group and the uplink transmission timing forthe PSTAG of the secondary cell group exceeds the maximum transmissiontiming difference, the terminal device 1 may consider that the thirdtimer for the PSTAG of the secondary cell group as expired to stop theuplink transmission for the PSTAG of the secondary cell group.Specifically, the terminal device 1 may stop the transmission on thePUSCH, PUCCH, and/or SRS for the PSTAG of the secondary cell group.

Here, the terminal device 1, which considers that the third timer forthe PSTAG of the secondary cell group as expired, may clear theconfigured uplink grant. In other words, the terminal device 1 may clearthe stored configured uplink grant. The terminal device 1, whichconsiders that the third timer for the PSTAG of the secondary cell groupas expired, may release (clear) the uplink resource (Semi-PersistentScheduling resource, PUSCH resource). As described above, theSemi-Persistent Scheduling may be performed in the primary secondarycell.

The terminal device 1, which considers that the third timer for thePSTAG of the secondary cell group as expired, may consider that thethird timer for the STAG of the secondary cell group as expired.Specifically, the terminal device 1 may stop the transmission on thePUSCH, PUCCH, and/or SRS for the STAG of the secondary cell group.

In a case that a difference between the uplink transmission timing forthe PTAG of the master cell group and the uplink transmission timing forthe STAG of the secondary cell group exceeds the maximum transmissiontiming difference, the terminal device 1 may consider that the thirdtimer for the STAG of the secondary cell group as expired, and may stopthe uplink transmission for the STAG of the secondary cell group.Specifically, the terminal device 1 may stop the transmission on thePUSCH, PUCCH, and/or SRS for the STAG of the secondary cell group.

In a case that a difference between the uplink transmission timing forthe STAG of the master cell group and the uplink transmission timing forthe PSTAG of the secondary cell group exceeds the maximum transmissiontiming difference, the terminal device 1 may consider that the thirdtimer for the PSTAG of the secondary cell group as expired and may stopthe uplink transmission for the PSTAG of the secondary cell group.Specifically, the terminal device 1 may stop the transmission on thePUSCH, PUCCH, and/or SRS for the PSTAG of the secondary cell group.

As described above, the terminal device 1, which considers that thethird timer for the PSTAG of the secondary cell group as expired, mayconsider that the third timer for the STAG of the secondary cell grouphas expired. Specifically, the terminal device 1 may stop thetransmission on the PUSCH, PUCCH, and/or SRS for the STAG of thesecondary cell group.

In a case that a difference between the uplink transmission timing forthe STAG of the master cell group and the uplink transmission timing forthe STAG of the secondary cell group exceeds the maximum transmissiontiming difference, the terminal device 1 may consider that the thirdtimer for the STAG of the secondary cell group as expired to stop theuplink transmission for the STAG of the secondary cell group.Specifically, the terminal device 1 may stop the transmission on thePUSCH, PUCCH, and/or SRS for the STAG of the secondary cell group.

In a case that a difference between the uplink transmission timing forthe PSTAG of the secondary cell group and the uplink transmission timingfor the STAG of the secondary cell group exceeds the maximumtransmission timing difference, the terminal device 1 may consider thatthe third timer for the STAG of the secondary cell group as expired andmay stop the uplink transmission for the STAG of the secondary cellgroup. Specifically, the terminal device 1 may stop the transmission onthe PUSCH, PUCCH, and/or SRS for the STAG of the secondary cell group.

In other words, for example, the cell groups and/or TAGs for which thethird timer is considered as expired may be prioritized. For example, asdescribed above, a prioritization may be made such as the PTAG of themaster cell group>the STAG of the master cell group>the PSTAG of thesecondary cell group>the STAG of the secondary cell group. Here, how thecell groups and/or TAGs are prioritized may be defined in advance byspecifications or the like. To be more specific, the prioritization ofthe cell groups and/or TAGs is not limited to that described above, and,of course, similar prioritization is included in the present embodiment.

As described above, the behavior described above with reference to thedrawings may be limited as behavior performed only in one serving cell(e.g., only primary cell). For example, only in a case that the behaviorcorresponding to the Semi-Persistent Scheduling and the behaviorcorresponding to the dynamic scheduling are performed in one servingcell, the behavior described above may apply. In other words, forexample, in a case that the behavior corresponding to theSemi-Persistent Scheduling is performed in a certain serving cell (e.g.,primary cell), and the behavior corresponding to the dynamic schedulingis performed in a serving cell different from the certain serving cell(e.g., secondary cell), the behavior described above may not apply.

The behavior described above may be behavior performed for multipleserving cells (e.g., the primary cell and the secondary cell). Forexample, even in the case that the behavior corresponding to theSemi-Persistent Scheduling is performed in a certain serving cell (e.g.,primary cell), and the behavior corresponding to the dynamic schedulingis performed in a serving cell (e.g., secondary cell) different from thecertain serving cell, the behavior described above may apply.

Structures of devices according to the present embodiment will bedescribed below.

FIG. 12 is a schematic block diagram illustrating a configuration of theterminal device 1 according to the present embodiment. As illustrated inFIG. 12, the terminal device 1 is configured to include a higher layerprocessing unit 101, a control unit 103, a reception unit 105, atransmission unit 107, and a transmit and receive antenna 109. Thehigher layer processing unit 101 is configured to include a radioresource control unit 1011, a scheduling information interpretation unit1013, and a SPS control unit 1015. The reception unit 105 is configuredto include a decoding unit 1051, a demodulation unit 1053, ademultiplexing unit 1055, a radio reception unit 1057, and a channelmeasurement unit 1059. The transmission unit 107 is configured toinclude a coding unit 1071, a modulation unit 1073, a multiplexing unit1075, a radio transmission unit 1077, and an uplink reference signalgeneration unit 1079.

The higher layer processing unit 101 outputs the uplink data (thetransport block) generated by a user operation or the like, to thetransmission unit 107. The higher layer processing unit 101 performsprocessing of the Medium Access Control (MAC) layer, the Packet DataConvergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer,and the Radio Resource Control (RRC) layer.

The radio resource control unit 1011 included in the higher layerprocessing unit 101 manages various configuration information/parametersof the terminal device 1 itself. The radio resource control unit 1011sets the various configuration information/parameters in accordance withhigher layer signaling received from the base station device 3. To bemore specific, the radio resource control unit 1011 sets the variousconfiguration information/parameters in accordance with the informationindicating the various configuration information/parameters receivedfrom the base station device 3. Furthermore, the radio resource controlunit 1011 generates information to be mapped to each uplink channel, andoutputs the generated information to the transmission unit 107. Theradio resource control unit 1011 is also referred to as a configurationunit 1011.

Here, the scheduling information interpretation unit 1013 included inthe higher layer processing unit 101 interprets the DCI format(scheduling information) received through the reception unit 105,generates control information for control of the reception unit 105 andthe transmission unit 107, in accordance with a result of interpretingthe DCI format, and outputs the generated control information to thecontrol unit 103.

The SPS control unit 1015 included in the higher layer processing unit101 performs controls concerning the SPS, based on various configurationinformation, and information or conditions regarding the SPS such asparameters.

In accordance with the control information originating from the higherlayer processing unit 101, the control unit 103 generates a controlsignal for control of the reception unit 105 and the transmission unit107. The control unit 103 outputs the generated control signal to thereception unit 105 and the transmission unit 107 to control thereception unit 105 and the transmission unit 107.

In accordance with the control signal input from the control unit 103,the reception unit 105 demultiplexes, demodulates, and decodes areception signal received from the base station device 3 through thetransmit and receive antenna 109, and outputs the information resultingfrom the decoding, to the higher layer processing unit 101.

The radio reception unit 1057 converts (down-converts) a downlink signalreceived through the transmit and receive antenna 109 into a basebandsignal through orthogonal demodulation, removes unnecessary frequencycomponents, controls an amplification level in such a manner as tosuitably maintain a signal level, performs orthogonal demodulation,based on an in-phase component and an orthogonal component of thereceived signal, and converts the resulting orthogonally-demodulatedanalog signal into a digital signal. The radio reception unit 1057removes a portion corresponding to a Cyclic Prefix (CP) from the digitalsignal resulting from the conversion, performs Fast Fourier Transform(FFT) on the signal from which the CP has been removed, and extracts asignal in the frequency domain.

The demultiplexing unit 1055 demultiplexes the extracted signal into thePHICH, the PDCCH, the EPDCCH, the PDSCH, and the downlink referencesignal. Moreover, the demultiplexing unit 1055 makes a compensation ofchannels including the PHICH, the PDCCH, the EPDCCH, and the PDSCH, froma channel estimate input from the channel measurement unit 1059.Furthermore, the demultiplexing unit 1055 outputs the downlink referencesignal resulting from the demultiplexing, to the channel measurementunit 1059.

The demodulation unit 1053 multiplies the PHICH by a corresponding codefor composition, demodulates the resulting composite signal incompliance with a Binary Phase Shift Keying (BPSK) modulation scheme,and outputs a result of the demodulation to the decoding unit 1051. Thedecoding unit 1051 decodes the PHICH destined for the terminal device 1itself and outputs the HARQ indicator resulting from the decoding to thehigher layer processing unit 101. The demodulation unit 1053 demodulatesthe PDCCH and/or the EPDCCH in compliance with a QPSK modulation schemeand outputs a result of the demodulation to the decoding unit 1051. Thedecoding unit 1051 attempts to decode the PDCCH and/or the EPDCCH. In acase of succeeding in the decoding, the decoding unit 1051 outputsdownlink control information resulting from the decoding and an RNTI towhich the downlink control information corresponds, to the higher layerprocessing unit 101.

The demodulation unit 1053 demodulates the PDSCH in compliance with amodulation scheme notified with the downlink grant, such as QuadraturePhase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), or64 QAM, and outputs a result of the demodulation to the decoding unit1051. The decoding unit 1051 decodes the data in accordance withinformation of a coding rate notified with the downlink controlinformation, and outputs, to the higher layer processing unit 101, thedownlink data (the transport block) resulting from the decoding.

The channel measurement unit 1059 measures a downlink path loss or achannel state from the downlink reference signal input from thedemultiplexing unit 1055, and outputs the measured path loss or channelstate to the higher layer processing unit 101. Furthermore, the channelmeasurement unit 1059 calculates a downlink channel estimate from thedownlink reference signal and outputs the calculated downlink channelestimate to the demultiplexing unit 1055. The channel measurement unit1059 performs channel measurement and/or interference measurement inorder to calculate the CQI (or the CSI).

The transmission unit 107 generates the uplink reference signal inaccordance with the control signal input from the control unit 103,codes and modulates the uplink data (the transport block) input from thehigher layer processing unit 101, multiplexes the PUCCH, the PUSCH, andthe generated uplink reference signal, and transmits a result of themultiplexing to the base station device 3 through the transmit andreceive antenna 109. Furthermore, the transmission unit 107 transmitsuplink control information.

The coding unit 1071 performs coding, such as convolutional coding orblock coding, on the uplink control information input from the higherlayer processing unit 101. Furthermore, the coding unit 1071 performsturbo coding in accordance with information used for the scheduling ofthe PUSCH.

The modulation unit 1073 modulates coded bits input from the coding unit1071, in compliance with the modulation scheme notified with thedownlink control information, such as BPSK, QPSK, 16 QAM, or 64 QAM, orin compliance with a modulation scheme prescribed in advance for eachchannel. In accordance with the information used for the scheduling ofthe PUSCH, the modulation unit 1073 determines the number of datasequences to be spatial-multiplexed, maps multiple pieces of uplink datato be transmitted on the same PUSCH to multiple sequences throughMultiple Input Multiple Output Spatial Multiplexing (MIMO SM), andperforms precoding on the sequences.

The uplink reference signal generation unit 1079 generates a sequenceacquired in accordance with a rule (formula) prescribed in advance,based on a physical layer cell identifier (also referred to as aPhysical Cell Identity (PCI), a Cell ID, or the like) for identifyingthe base station device 3, a bandwidth to which the uplink referencesignal is mapped, a cyclic shift notified with the uplink grant, aparameter value for generation of a DMRS sequence, and the like. Inaccordance with the control signal input from the control unit 103, themultiplexing unit 1075 rearranges modulation symbols of the PUSCH inparallel and then performs Discrete Fourier Transform (DFT) on therearranged modulation symbols. Furthermore, the multiplexing unit 1075multiplexes PUCCH and PUSCH signals and the generated uplink referencesignal for each transmit antenna port. To be more specific, themultiplexing unit 1075 maps the PUCCH and PUSCH signals and thegenerated uplink reference signal to the resource elements for eachtransmit antenna port.

The radio transmission unit 1077 performs Inverse Fast Fourier Transform(IFFT) on a signal resulting from the multiplexing, generates an SC-FDMAsymbol, attaches a CP to the generated SC-FDMA symbol, generates abaseband digital signal, converts the baseband digital signal into ananalog signal, removes unnecessary frequency components through alowpass filter, up-converts a result of the removal into a signal of acarrier frequency, performs power amplification, and outputs a finalresult to the transmit and receive antenna 109 for transmission.

FIG. 13 is a schematic block diagram illustrating a configuration of thebase station device 3 according to the present embodiment. Asillustrated in the figure, the base station device 3 is configured toinclude a higher layer processing unit 301, a control unit 303, areception unit 305, a transmission unit 307, and a transmit and receiveantenna 309. The higher layer processing unit 301 is configured toinclude a radio resource control unit 3011, a scheduling unit 3013, anda SPS control unit 3015. The reception unit 305 is configured to includea decoding unit 3051, a demodulation unit 3053, a demultiplexing unit3055, a radio reception unit 3057, and a channel measurement unit 3059.The transmission unit 307 is configured to include a coding unit 3071, amodulation unit 3073, a multiplexing unit 3075, a radio transmissionunit 3077, and a downlink reference signal generation unit 3079.

The higher layer processing unit 301 performs processing of the MediumAccess Control (MAC) layer, the Packet Data Convergence Protocol (PDCP)layer, the Radio Link Control (RLC) layer, and the Radio ResourceControl (RRC) layer. Furthermore, the higher layer processing unit 301generates control information for control of the reception unit 305 andthe transmission unit 307, and outputs the generated control informationto the control unit 303.

The radio resource control unit 3011 included in the higher layerprocessing unit 301 generates, or acquires from a higher node, thedownlink data (the transport block) mapped to the downlink PDSCH, systeminformation, the RRC message, the MAC CE (element for control), and thelike, and outputs a result of the generation or the acquirement to thetransmission unit 307. Furthermore, the radio resource control unit 3011manages various configuration information/parameters for each of theterminal devices 1. The radio resource control unit 3011 may configurevarious configuration information/parameters for each of the terminaldevices 1 through higher layer signaling. In other words, the radioresource control unit 1011 transmits/broadcasts information indicatingvarious configuration information/parameters. The radio resource controlunit 3011 is also referred to as a configuration unit 3011.

The scheduling unit 3013 included in the higher layer processing unit301 determines a frequency and a subframe to which the physical channels(PDSCH and PUSCH) are allocated, the coding rate and modulation schemefor the physical channels (PDSCH and PUSCH), the transmit power, and thelike, from the received channel state information and from the channelestimate, channel quality, or the like input from the channelmeasurement unit 3059. The scheduling unit 3013 generates the controlinformation (e.g., the DCI format) in order to control the receptionunit 305 and the transmission unit 307 in accordance with a result ofthe scheduling, and outputs the generated information to the controlunit 303. The scheduling unit 3013 further determines timing ofperforming transmission processing and reception processing.

The SPS control unit 3015 included in the higher layer processing unit301 performs controls concerning the SPS, based on various configurationinformation, and information or conditions regarding the SPS such asparameters.

In accordance with the control information originating from the higherlayer processing unit 301, the control unit 303 generates a controlsignal for control of the reception unit 305 and the transmission unit307. The control unit 303 outputs the generated control signal to thereception unit 305 and the transmission unit 307 to control thereception unit 305 and the transmission unit 307.

In accordance with the control signal input from the control unit 303,the reception unit 305 demultiplexes, demodulates, and decodes thereception signal received from the terminal device 1 through thetransmit and receive antenna 309, and outputs information resulting fromthe decoding to the higher layer processing unit 301. The radioreception unit 3057 converts (down-converts) an uplink signal receivedthrough the transmit and receive antenna 309 into a baseband signalthrough orthogonal demodulation, removes unnecessary frequencycomponents, controls the amplification level in such a manner as tosuitably maintain a signal level, performs orthogonal demodulation,based on an in-phase component and an orthogonal component of thereceived signal, and converts the resulting orthogonally-demodulatedanalog signal into a digital signal. The reception unit 305 receives theuplink control information.

The radio reception unit 3057 removes a portion corresponding to aCyclic Prefix (CP) from the digital signal resulting from theconversion. The radio reception unit 3057 performs Fast FourierTransform (FFT) on the signal from which the CP has been removed,extracts a signal in the frequency domain, and outputs the resultingsignal to the demultiplexing unit 3055.

The demultiplexing unit 1055 demultiplexes the signal input from theradio reception unit 3057 into the PUCCH, the PUSCH, and the signal suchas the uplink reference signal. The demultiplexing is performed based onradio resource allocation information that is determined in advance bythe base station device 3 using the radio resource control unit 3011 andthat is included in the uplink grant notified to each of the terminaldevices 1. Furthermore, the demultiplexing unit 3055 makes acompensation of channels including the PUCCH and the PUSCH from thechannel estimate input from the channel measurement unit 3059.Furthermore, the demultiplexing unit 3055 outputs an uplink referencesignal resulting from the demultiplexing, to the channel measurementunit 3059.

The demodulation unit 3053 performs Inverse Discrete Fourier Transform(IDFT) on the PUSCH, acquires modulation symbols, and performs receptionsignal demodulation, that is, demodulates each of the modulation symbolson the PUCCH and the PUSCH, in compliance with the modulation schemeprescribed in advance, such as Binary Phase Shift Keying (BPSK), QPSK,16 QAM, or 64 QAM, or in compliance with the modulation scheme that thebase station device 3 itself notified in advance with the uplink granteach of the terminal devices 1. The demodulation unit 3053 demultiplexesthe modulation symbols of multiple pieces of uplink data transmitted onthe same PUSCH with the MIMO SM, based on the number ofspatial-multiplexed sequences notified in advance with the uplink grantto each of the terminal devices 1 and information designating theprecoding to be performed on the sequences.

The decoding unit 3051 decodes the coded bits of the PUCCH and thePUSCH, which have been demodulated, at the coding rate in compliancewith a coding scheme prescribed in advance, the coding rate beingprescribed in advance or being notified in advance with the uplink grantto the terminal device 1 by the base station device 3 itself, andoutputs the decoded uplink data and uplink control information to thehigher layer processing unit 101. In a case where the PUSCH isre-transmitted, the decoding unit 3051 performs the decoding with thecoded bits input from the higher layer processing unit 301 and retainedin an HARQ buffer, and the demodulated coded bits. The channelmeasurement unit 309 measures the channel estimate, the channel quality,and the like, based on the uplink reference signal input from thedemultiplexing unit 3055, and outputs a result of the measurement to thedemultiplexing unit 3055 and the higher layer processing unit 301.

The transmission unit 307 generates the downlink reference signal inaccordance with the control signal input from the control unit 303,codes and modulates the HARQ indicator, the downlink controlinformation, and the downlink data that are input from the higher layerprocessing unit 301, multiplexes the PHICH, the PDCCH, the EPDCCH, thePDSCH, and the downlink reference signal, and transmits a result of themultiplexing to the terminal device 1 through the transmit and receiveantenna 309.

The coding unit 3071 codes the HARQ indicator, the downlink controlinformation, and the downlink data that are input from the higher layerprocessing unit 301, in compliance with the coding scheme prescribed inadvance, such as block coding, convolutional coding, or turbo coding, orin compliance with the coding scheme determined by the radio resourcecontrol unit 3011. The modulation unit 3073 modulates the coded bitsinput from the coding unit 3071, in compliance with the modulationscheme prescribed in advance, such as BPS K, QPSK, 16 QAM, or 64 QAM, orin compliance with the modulation scheme determined by the radioresource control unit 3011.

The downlink reference signal generation unit 3079 generates, as thedownlink reference signal, a sequence that is already known to theterminal device 1 and that is acquired in accordance with a ruleprescribed in advance, based on the Physical layer Cell Identifier (PCI)for identifying the base station device 3, and the like. Themultiplexing unit 3075 multiplexes the modulated modulation symbol ofeach channel and the generated downlink reference signal. To be morespecific, the multiplexing unit 3075 maps the modulated modulationsymbol of each channel and the generated downlink reference signal tothe resource elements.

The radio transmission unit 3077 performs Inverse Fast Fourier Transform(IFFT) on the modulation symbol resulting from the multiplexing or thelike, generates an OFDM symbol, attaches a CP to the generated OFDMsymbol, generates a baseband digital signal, converts the basebanddigital signal into an analog signal, removes unnecessary frequencycomponents through a lowpass filter, up-converts a result of the removalinto a signal of a carrier frequency, performs power amplification, andoutputs a final result to the transmit and receive antenna 309 fortransmission.

To be more specific, the terminal device 1 according to the presentembodiment includes the higher layer processing unit 101 configured tostore the uplink grant received from the base station device as theconfigured uplink grant, a transmission unit 107 configured to performthe transmission of the MAC protocol data unit, based on the configureduplink grant that is considered to occur in a subframe satisfying aprescribed condition, the transmission unit 107 transmitting the MACprotocol data unit based on the configured uplink grant in response toreceiving the uplink grant that is used to indicate a release of theSemi-Persistent Scheduling, and the higher layer processing unit 101configured to clear the configured uplink grant. The field of theresource allocation information included in the uplink grant that isused to indicate the release of the Semi-Persistent Scheduling is set toa prescribed value defined for the release of the Semi-PersistentScheduling.

The base station device 3 according to the present embodiment includesthe higher layer processing unit 301 configured to consider that theuplink grant transmitted to the terminal device 1 is to be stored as aconfigured uplink grant, a reception unit 305 configured to perform thereception of the MAC protocol data unit, based on the configured uplinkgrant that is considered to occur in a subframe satisfying a prescribedcondition, the reception unit 305 receiving the MAC protocol data unit,based on the configured uplink grant in response to transmitting theuplink grant that is used to indicate a release of the Semi-PersistentScheduling, and the higher layer processing unit 301 configured toconsider the configured uplink grant to be cleared. The field of theresource allocation information included in the uplink grant that isused to indicate the release of the Semi-Persistent Scheduling is set toa prescribed value defined for the release of the Semi-PersistentScheduling.

The terminal device 1 according to the present embodiment includes thereception unit 105 configured to receive a first parameter forindicating the number of empty transmissions before a release, and asecond parameter for configuring the first counter, the higher layerprocessing unit 101 which is configured with the first parameter, andconfigured to clear the configured uplink grant in the case that thenumber of consecutive empty transmissions based on the configured uplinkgrant reaches a value indicated using the first parameter, and thehigher layer processing unit 101 being configured with the secondparameter, and clear the configured uplink grant in the case that thenumber of occurrences of the configured uplink grant reaches the valueindicated using the second parameter. Each of the consecutive emptytransmissions corresponds to an initial transmission, and is thetransmission of the MAC protocol data unit not including firstprescribed information.

The terminal device 1 according to the present embodiment includes thehigher layer processing unit 101 configured to receive a first parameterfor indicating the number of empty transmissions before a release and asecond parameter for configuring the first timer, is configured with thefirst parameter, and configured to clear the configured uplink grant inthe case that the number of consecutive empty transmissions based on theconfigured uplink grant reaches the value indicated using the firstparameter, and the higher layer processing unit 101 being configuredwith the second parameter, and clears the configured uplink grant in thecase that a timer indicated using the second parameter has expired. Eachof the consecutive empty transmissions corresponds to an initialtransmission, and is the transmission of the MAC protocol data unit notincluding the first prescribed information.

The base station device 3 according to the present embodiment includesthe transmission unit 307 configured to transmit a first parameter forindicating the number of empty transmissions before a release, and asecond parameter for configuring a first counter, and the higher layerprocessing unit 301 which configures a first parameter, and configuredto consider that the configured uplink grant is to be cleared in thecase that the number of consecutive empty transmissions based on theconfigured uplink grant reaches a value indicated using the firstparameter, the higher layer processing unit 301 configuring a secondparameter, and considering that the configured uplink grant is to becleared in a case that the number of occurrences of the configureduplink grant reaches a value indicated using the second parameter. Eachof the consecutive empty transmissions corresponds to an initialtransmission, and is transmission of the MAC protocol data unit notincluding the first prescribed information.

The base station device 3 according to the present embodiment includesthe transmission unit 307 configured to transmit a first parameter forindicating the number of empty transmissions before a release, and asecond parameter for configuring a first timer, and the higher layerprocessing unit 301 which configures the first parameter, and considersthat the configured uplink grant is to be cleared in the case that thenumber of consecutive empty transmissions based on the configured uplinkgrant reaches a value indicated using the first parameter, the higherlayer processing unit 301 configuring the second parameter, andconsidering that the configured uplink grant is to be cleared in a casethat a timer indicated using a second parameter has expired. Each of theconsecutive empty transmissions corresponds to an initial transmission,and is transmission of the MAC protocol data unit not including thefirst prescribed information.

The terminal device 1 according to the present embodiment includes thehigher layer processing unit 101 configured to store the uplink grantreceived from a base station device, as the configured uplink grant, andthe transmission unit 107 configured to transmit the MAC protocol dataunit including prescribed information based on the configured uplinkgrant considered to occur in a subframe satisfying a prescribedcondition, while the timer is not running, the transmission unit 107 nottransmitting the MAC protocol data unit based on the configured uplinkgrant considered to occur in the subframe satisfying the prescribedcondition while the timer is running regardless of whether theprescribed information is included in the MAC protocol data unit. Thetimer is started, based on the transmission of the MAC protocol dataunit including the prescribed information.

The transmission unit 107 is configured to transmit the MAC protocoldata unit based on the configured uplink grant in response to the uplinkgrant that is used to indicate activation or reactivation of theSemi-Persistent Scheduling regardless of whether the timer is running orwhether the prescribed information is included in the MAC protocol dataunit.

The transmission unit 107 is configured to transmit the MAC protocoldata unit based on the configured uplink grant in response to the uplinkgrant that is used to indicate a release of the Semi-PersistentScheduling regardless of whether the timer is running or whether theprescribed information is included in the MAC protocol data unit, andthe higher layer processing unit 101 is configured to stop the timer.

The base station device 3 according to the present embodiment includesthe higher layer processing unit 301 configured to consider an uplinkgrant transmitted to the terminal device to be stored as the configureduplink grant, and the reception unit 305 configured to receive the MACprotocol data unit including prescribed information based on theconfigured uplink grant considered to occur in a subframe satisfying aprescribed condition, while the timer is not running, the reception unit305 not receiving the MAC protocol data unit based on the configureduplink grant considered to occur in the subframe satisfying theprescribed condition while the timer is running regardless of whetherthe prescribed information is included in the MAC protocol data unit.The timer is started, based on the reception of the MAC protocol dataunit including the prescribed information.

The reception unit 305 is configured to receive the MAC protocol dataunit based on the configured uplink grant in response to transmittingthe uplink grant that is used to indicate activation or reactivation ofthe Semi-Persistent Scheduling regardless of whether the timer isrunning or whether the prescribed information is included in the MACprotocol data unit.

The reception unit 305 is configured to receive the MAC protocol dataunit based on the configured uplink grant in response to transmittingthe uplink grant that is used to indicate a release of theSemi-Persistent Scheduling regardless of whether the timer is running orwhether the prescribed information is included in the MAC protocol dataunit, and the higher layer processing unit 301 is configured to stop thetimer.

The terminal device 1 according to the present embodiment includes thereception unit 105 configured to receive parameters for configuring themaster cell group and secondary cell group, a parameter for configuringthe Timing Advance Groups, and a parameter for configuring the timer foreach of the Timing Advance Groups, and the higher layer processing unit101 configured to store the uplink grant received in the primarysecondary cell of the secondary cell group as the configured uplinkgrant, the higher layer processing unit 101 considering that the timerfor the Primary Secondary Timing Advance Group of the secondary cellgroup has expired and clearing the configured uplink grant, in a casethat the difference between the uplink transmission timing for thePrimary Timing Advance Group of the master cell group and the uplinktransmission timing for the Primary Secondary Timing Advance Group ofthe secondary cell group exceeds a maximum transmission timingdifference.

The terminal device 1 also includes the transmission unit 107 configuredto consider that the timer for the Secondary Timing Advance Group of themaster cell group has expired, and to stop the transmission on thePUSCH, PUCCH, and/or SRS for the Secondary Timing Advance Group of themaster cell group, in a case that the difference between the uplinktransmission timing for the Primary Timing Advance Group of the mastercell group and the uplink transmission timing for the Secondary TimingAdvance Group of the master cell group exceeds the maximum transmissiontiming difference.

The terminal device 1 also includes the transmission unit 107 configuredto consider that the timer for the Secondary Timing Advance Group of thesecondary cell group has expired, and to stop the transmission on thePUSCH, PUCCH, and/or SRS for the Secondary Timing Advance Group of thesecondary cell group, in the case that the difference between the uplinktransmission timing for the Primary Timing Advance Group of the mastercell group and the uplink transmission timing for the Secondary TimingAdvance Group of the secondary cell group exceeds the maximumtransmission timing difference.

The base station device 3 according to the present embodiment includesthe transmission unit 307 configured to transmit the parameters forconfiguring the master cell group and secondary cell group, theparameter for configuring the Timing Advance Groups, and the parameterfor configuring the timer for each of the Timing Advance Groups, and thehigher layer processing unit 301 configured to consider that the uplinkgrant transmitted in the primary secondary cell of the secondary cellgroup is to be stored as the configured uplink grant, the higher layerprocessing unit 301 considering that the timer for the Primary SecondaryTiming Advance Group of the secondary cell group has expired andconsidering that the configured uplink grant is to be cleared, in thecase that the difference between the uplink transmission timing for thePrimary Timing Advance Group of the master cell group and the uplinktransmission timing for the Primary Secondary Timing Advance Group ofthe secondary cell group exceeds the maximum transmission timingdifference.

The base station device 3 also includes the higher layer processing unit301 configured to consider that the timer for the Secondary TimingAdvance Group of the master cell group has expired, and to consider thatthe transmission on the PUSCH, PUCCH, and/or SRS for the SecondaryTiming Advance Group of the master cell group is to be stopped, in thecase that the difference between the uplink transmission timing for thePrimary Timing Advance Group of the master cell group and the uplinktransmission timing for the Secondary Timing Advance Group of the mastercell group exceeds the maximum transmission timing difference.

The base station device 3 also includes the higher layer processing unit301 configured to consider that the timer for the Secondary TimingAdvance Group of the secondary cell group has expired, and to considerthe transmission on the PUSCH, PUCCH, and/or SRS for the SecondaryTiming Advance Group of the secondary cell group to be stopped, in thecase that the difference between the uplink transmission timing for thePrimary Timing Advance Group of the master cell group and the uplinktransmission timing for the Secondary Timing Advance Group of thesecondary cell group exceeds the maximum transmission timing difference.

This allows the uplink data to be efficiently transmitted.

A program running on each of the base station device 3 and the terminaldevice 1 according to the present invention may serve as a program thatcontrols a Central Processing Unit (CPU) and the like (a program forcausing a computer to operate) in such a manner as to enable thefunctionalities according to the above-described embodiment of thepresent invention. The information handled in these devices istemporarily stored in a Random Access Memory (RAM) while beingprocessed. Thereafter, the information is stored in various types ofRead Only Memory (ROM) such as a flash ROM and a Hard Disk Drive (HDD),and when necessary, is read by the CPU to be modified or rewritten.

Moreover, the terminal device 1 and the base station device 3 accordingto the above-described embodiment may be partially achieved by acomputer. In this case, this configuration may be realized by recordinga program for realizing such control functions on a computer-readablerecording medium and causing a computer system to read the programrecorded on the recording medium for execution.

Note that it is assumed that the “computer system” refers to a computersystem built into the terminal device 1 or the base station device 3,and the computer system includes an OS and hardware components such as aperipheral device. Furthermore, the “computer-readable recording medium”refers to a portable medium such as a flexible disk, a magneto-opticaldisk, a ROM, and a CD-ROM, and a storage device such as a hard diskbuilt into the computer system.

Moreover, the “computer-readable recording medium” may include a mediumthat dynamically retains the program for a short period of time, such asa communication line that is used to transmit the program over a networksuch as the Internet or over a communication line such as a telephoneline, and a medium that retains, in that case, the program for a fixedperiod of time, such as a volatile memory within the computer systemwhich functions as a server or a client. Furthermore, the program may beconfigured to realize some of the functions described above, and alsomay be configured to be capable of realizing the functions describedabove in combination with a program already recorded in the computersystem.

Furthermore, the base station device 3 according to the above-describedembodiment is achieved as an aggregation (a device group) constituted ofmultiple devices. Devices constituting such a device group may be eachequipped with some or all portions of each function or each functionalblock of the base station device 3 according to the above-describedembodiment. The device group may include at least generalfunctionalities or general functional blocks of the base station device3. Furthermore, the terminal device 1 according to the above-describedembodiments can also communicate with the base station device as theaggregation.

Furthermore, the base station device 3 according to the above-describedembodiment may serve as an Evolved Universal Terrestrial Radio AccessNetwork (EUTRAN). Furthermore, the base station device 3 according tothe above-described embodiment may have some or all portions of thefunctionalities of a node higher than an eNodeB.

Furthermore, some or all portions of each of the terminal device 1 andthe base station device 3 according to the above-described embodimentmay be achieved as an LSI which is a typical integrated circuit or maybe achieved as a chip set. The functional blocks of each of the terminaldevice 1 and the base station device 3 may be individually achieved as achip, or some or all of the functional blocks may be integrated into achip. Furthermore, a circuit integration technique is not limited to theLSI, and may be realized with a dedicated circuit or a general-purposeprocessor. Furthermore, in a case where with advances in semiconductortechnology, a circuit integration technology with which an LSI isreplaced appears, it is also possible to use an integrated circuit basedon the technology.

Furthermore, according to the above-described embodiment, the terminaldevice has been described as an example of a communication device, butthe present invention is not limited to such a terminal device, and isapplicable to a terminal device or a communication device of afixed-type or a stationary-type electronic apparatus installed indoorsor outdoors, for example, such as an Audio-Video (AV) apparatus, akitchen apparatus, a cleaning or washing machine, an air-conditioningapparatus, office equipment, a vending machine, and other householdapparatuses.

The embodiments of the present invention have been described in detailabove referring to the drawings, but the specific configuration is notlimited to the embodiments and includes, for example, an amendment to adesign that falls within the scope that does not depart from the gist ofthe present invention. Furthermore, various modifications are possiblewithin the scope of the present invention defined by claims, andembodiments that are made by suitably combining technical meansdisclosed according to the different embodiments are also included inthe technical scope of the present invention. Furthermore, aconfiguration in which a constituent element that achieves the sameeffect is substituted for the one that is described according to theembodiments is also included in the technical scope of the presentinvention.

REFERENCE SIGNS LIST

-   1 (1A, 1B, 1C) Terminal device-   3 Base station device-   101 Higher layer processing unit-   103 Control unit-   105 Reception unit-   107 Transmission unit-   301 Higher layer processing unit-   303 Control unit-   305 Reception unit-   307 Transmission unit-   1011 Radio resource control unit-   1013 Scheduling information interpretation unit-   1015 SPS control unit-   3011 Radio resource control unit-   3013 Scheduling unit-   3015 SPS control unit

1. A terminal device that communicates with a base station device in adual connectivity, the terminal device comprising: transmissioncircuitry configured to perform a physical uplink shared channel (PUSCH)transmission; and control circuitry, wherein the control circuitry isconfigured to stop the PUSCH transmission for a timing advance group ofa secondary cell group in a case that a difference between an uplinktransmission timing for a timing advance group of a master cell groupand an uplink transmission timing for the timing advance group of thesecondary cell group exceeds a maximum transmission timing difference,the master cell group includes a primary cell, and the secondary cellgroup includes a primary secondary cell.
 2. The terminal deviceaccording to claim 1, wherein the control circuitry is configured toconsider that a timer for the timing advance group of the secondary cellgroup as expired in the case that the difference between the uplinktransmission timing for the timing advance group of the master cellgroup and the uplink transmission timing for the timing advance group ofthe secondary cell group exceeds the maximum transmission timingdifference.
 3. A base station device that communicates with a terminaldevice in a dual connectivity, the base station device comprising:reception circuitry configured to receive a physical uplink shredchannel transmission (PUSCH); and control circuitry, wherein the controlcircuitry is configured to consider that the PUSCH transmission for atiming advance group of a secondary cell group as stopped in a case thata difference between an uplink transmission timing for a timing advancegroup of a master cell group and an uplink transmission timing for thetiming advance group of the secondary cell group exceeds a maximumtransmission timing difference, the master cell group includes a primarycell, and the secondary cell group includes a primary secondary cell. 4.The base station device according to claim 3, wherein the controlcircuitry is configured to consider that a timer for the timing advancegroup of the secondary cell group as expired in the case that thedifference between the uplink transmission timing for the timing advancegroup of the master cell group and the uplink transmission timing forthe timing advance group of the secondary cell group exceeds the maximumtransmission timing difference.
 5. A communication method of a terminaldevice that communicates with a base station device in a dualconnectivity, the communication method comprising: performing a physicaluplink shared channel (PUSCH) transmission; and stopping the PUSCHtransmission for a timing advance group of a secondary cell group in acase that a difference between an uplink transmission timing for atiming advance group of a master cell group and an uplink transmissiontiming for the timing advance group of the secondary cell group exceedsa maximum transmission timing difference, wherein the master cell groupincludes a primary cell, and the secondary cell group includes a primarysecondary cell.
 6. The communication method according to claim 5,further comprising: considering that a timer for the timing advancegroup of the secondary cell group as expired in the case that thedifference between the uplink transmission timing for the timing advancegroup of the master cell group and the uplink transmission timing forthe timing advance group of the secondary cell group exceeds the maximumtransmission timing difference.
 7. A communication method of a basestation device that communicates with a terminal device in a dualconnectivity, the communication method comprising: receiving a physicaluplink shred channel (PUSCH) transmission; and considering that thePUSCH transmission for a timing advance group of a secondary cell groupas stopped in a case that a difference between an uplink transmissiontiming for a timing advance group of a master cell group and an uplinktransmission timing for the timing advance group of the secondary cellgroup exceeds a maximum transmission timing difference, wherein themaster cell group includes a primary cell, and the secondary cell groupincludes a primary secondary cell.
 8. The communication method accordingto claim 7, further comprising: considering that a timer for the timingadvance group of the secondary cell group as expired in the case thatthe difference between the uplink transmission timing for the timingadvance group of the master cell group and the uplink transmissiontiming for the timing advance group of the secondary cell group exceedsthe maximum transmission timing difference.